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, confirm the delivery purpose, target size or duration, scope of modification, 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 wordcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/wordcraft-skills --skill wordcraft-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.
Execution steps
- Confirm the target position, and retain real experience and dates.
- Organize content by summary, skills, experience, and projects, highlighting verifiable achievements.
- Use consistent date and heading formats, and control the density to one or two pages.
- Check reading order and text selection behavior.
Tool implementation
Use open_document/new_document to manage documents; verify with get_text, input with type_text, and perform other edits according to the live tool list; save with save_document, and check layout with render_page.
First read the actual tool schema, then fill in parameters; use the returned values for object or document IDs. The queried commands must be available on the current backend. Before saving, choose a new output path and preserve the input. If a required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as the real thing.
Result checking
- Do not fabricate education, job titles, or quantified achievements.
- Contact information is complete, and the font size is suitable for reading.
- Deliver an editable version and a PDF, and avoid having important content only in images.
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, first check the current project to avoid repeating irreversible operations.
Delivery
Return the editable project, the actual derived files, and a brief explanation: what modifications were made, which steps were not executed 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 requests rework, read this source project and make local modifications, preserving the content that has been accepted.