Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking within.
Task starting point
First read the assets, confirm the delivery purpose, target size or duration, modification scope, and required format. Details that can be determined from the task and assets should directly adopt reasonable defaults; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off to the pdfcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/pdfcraft-skills --skill pdfcraft-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 purpose and delivery specifications, and check the page count and page size.
- Check the crop box, bleed, fonts, and image resolution.
- Spot-check transparency effects, thin lines, and colors, and record characteristics that cannot be inspected.
- Reopen the exported file and check every page.
Tool implementation
The upstream tool name belongs to PdfCraft. doc_open/doc_create return a doc handle; subsequent doc_info, doc_save, and page_render use the same doc. PDF page numbers start from 1, and parameters are subject to the actual schema.
First read the actual tool schema, then fill in the parameters; use the returned values for object or document IDs. The queried commands must be available in the current backend. Before saving, choose a new output path and keep the input. When the required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as the real thing.
Result checking
- No unexpected blank areas, cropping, or missing characters.
- Do not mislabel an ordinary PDF as PDF/A or PDF/X compliant.
- Delivery check results and clearly identified unverified items.
Check the actual content against the user's goal, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the full page; for time-based media, inspect the start, end, and key segments. For abnormal results, first check the current project 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 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 reworks it, read this source project and make local modifications, preserving the accepted content.
Skill store scenario experience
When encountering dual-path text and visual verification, readStore workflow adaptation, and use the corresponding Craft method and actual result checking. Upstream skills are not used as runtime dependencies.
main development candidate supplement
When using the new candidate to count the word count of specified pages, find unmarked content, or check form labels, readmain new tools and processes. Distinguish MCP tool names from engine command IDs, and check the actual tool schema; do not treat the existence of a directory as accessibility certification.