Oda builds and edits Word, Excel and PowerPoint files in your workspace, and can check a finished file before you open it. The check is structural, so it confirms the file's structure and text, not its appearance.
| You ask for | Oda can make |
|---|---|
| A Word document | Reports, letters and formatted tables (.) |
| A PowerPoint presentation | Slides with text, tables, images and charts (.) |
| An Excel workbook | Cell values, formulas and formatting (.) |
Oda can run a check on a finished file. The check is read-only, looks inside the file's structure, and gives a verdict of pass or fail (exit code 0 when everything passed, 1 when a check failed, and 2 when the check request itself was wrong).
It reports four checks:
package: the file is a readable Office package, with all its parts present.contains: the text you asked to find is in the file.count: the number of slides or sheets.output: the check's report was saved.The check is strict about what it accepts:
input must be ..--count must be non-negative and applies only to slides or sheets.--out must differ from the input document.A passing check says the structure and the text are in order. It does not judge pagination, clipping, fonts, chart appearance or how Excel recalculates values, and it does not evaluate formulas. Open the file to see the finished result.
Document work runs on a bundled runtime, not on software already on your computer. Oda prepares its own copy of Python 3.9 or later with the libraries these skills need, and Node.js and pnpm when the app provides them. The preparation appears in the chat as Load workspace dependencies, and it returns the paths Oda will use. The first document task prepares the copy; later tasks reuse it.
primary runtime: incompatible platform or architecture when the copy does not fit this
computer, or workspace dependencies: source and root must be absolute paths when a location it
needs is not a full path.Ask in the chat, for example Check that the presentation has 12 slides or Check that the report contains the payment terms. Oda runs the check and tells you the verdict. If a check fails, ask Oda to fix the file and check it again.
No. The check is structural: it does not judge pagination, clipping, fonts, chart appearance or how Excel recalculates values. Open the file to see the finished result.
No. Oda writes the formula, but nothing calculates it until the workbook is opened in Excel. The check does not evaluate formulas, so a formula cell can look empty or stale in another tool until then.
No. The check covers ., . and . only, and legacy, encrypted and macro-enabled
files need their own workflow. Renaming a file does not convert it.
No. The check only reads the file. It never modifies the document it checks.
It names the check that failed and what it found. Ask Oda to fix the file and run the check again.
Close it first, or ask Oda to save a new copy. Excel locks an open workbook, so a save over the open file can fail.
In your workspace, together with any scripts and working files it uses for the task.
No. Oda prepares and manages its own bundled copy, so nothing is installed into your own setup, and PATH is never changed.
Oda keeps serving the previous complete copy for one more task and retries on the next. If the copy cannot be used at all, Oda reports the reason instead of working around it.
Text checks read the main part of the document, plus the headers, footers and notes it links to. Text in comments, in a glossary or in unreferenced parts of a Word file does not count, and in a presentation, chart text and speaker notes are not searched. Put the text in the document body or on a slide and check again.