Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking described therein.
Task starting point
First read the materials and confirm the delivery purpose, target size or duration, modification scope, and required format. Directly adopt reasonable defaults for details that can be determined from the task and materials; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off to the deckcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/deckcraft-skills --skill deckcraft-editor. The currently added skill is a local candidate; before release, use the local companion plugin and do not treat this installation command as proof of release.
Generate a command plan from real data
Use the skill's bundled scripts/data_story.py, without relying on other skill scripts:
python3 <本技能目录>/scripts/data_story.py --input data.json --output plan.json
For the input structure, see fillable example。title are user-provided conclusions pending verification;unit、period、source、definition、limitations、action is required. Preserve category order, with 2 to 12 categories and 1 to 3 groups of values on the same basis; reject missing values, duplicate categories, boolean values, and non-finite numbers, and do not fill missing values with zero. The compiler does not verify whether sources are true or false, nor does it infer causality. Long titles still require preview adjustment.
The plan is limited to new documents and includes file.new; it must not be executed directly against an existing editing session. After confirming creation, the CLI passes run --cmd <command>=<JSON params> --save <新路径>item by item via argv; when synchronized visuals are needed, use run_commanditem by item in the same session after the editor is ready, and do not start a separate CLI to fake synchronization. The output plan uses exclusive creation and does not overwrite existing files.
Charts are saved as native categorical bar charts; when the total number of data points is greater than 12, value labels are disabled by default to reduce overlap of dense labels, and exact values remain in the editable chart data. Still check the layout of identical values or long labels. Units go into the title; period, source, basis, and interpretation boundaries go into per-page notes. After saving, check the chart values and notes, and preview all pages; the actual chart axes, fonts, and projection effects still require separate acceptance.
Execution steps
- Verify metric definitions, periods, and filter scope.
- Write the conclusion first, then choose the chart that best supports it.
- Highlight key changes and note the baseline; add explanations for outliers.
- Finally, provide action recommendations that can be supported by the data.
Tool implementation
Use open_presentation/new_presentation to manage presentations; use add_slide, inspect_slide, and inspect_document to operate and verify; use save_presentation to save.
Read the actual tool schema first, then fill in parameters; use returned values for object or document IDs. Queried commands must be available on the current backend. Before saving, choose a new output path and preserve the input. When a required algorithm, format, or command does not exist, state the gap and do not pass off a similar name as a substitute.
Result checking
- Chart axes and values are accurate, and missing values are not drawn as zero.
- Correlation is not written as causation.
- Each page's conclusion is consistent with the evidence.
Check the actual content against the user's goals, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the whole page; for time-based media, inspect the start, end, and key segments. For abnormal results, check the current project first to avoid repeatedly performing irreversible operations.
Delivery
Return the editable project, the actual derived files, and a brief explanation: what modifications were made, which steps were not performed due to current capabilities, and what requires the user's judgment. List only files that actually exist and have been checked. If the user subsequently reworks it, read the source project from this session and modify it locally, preserving the content that has already been accepted.