First readthe specific methods, parameters, and boundariesthen follow thestructured stepsto execute. The values, file names, and titles are examples and must be replaced according to the current input; the examples must not be treated as actual business facts.
Input and execution
The user provided a multi-page invoice or document bundle and the starting page of each document, and the documents need to be delivered separately without missing any pages. First verify the input file, the scope of modifications approved by the user, and the target output. The boundary table is confirmed input; do not guess document boundaries based on blank pages or numeric amounts. Splitting does not verify tax authenticity or judge reimbursement compliance; for encrypted/signed documents, first confirm the output requirements, and use a new directory for output.
Keep a single native CLI script or the same MCP session, and use the ID actually returned by the current doc_open. The CLI compiler's document slot applies only to the brand-new process script it generates, not to an already running editor ID. When a tool is missing, report the gap; do not impersonate it with a similar command.
Verification and delivery
Reopen the three outputs, with 2/1/3 pages respectively; the page-by-page identification order is exactly the same as the original pages 1-6, with no pages lost and no crossing between documents; the source PDF bytes remain unchanged.
Deliver the actually existing new outputs and a brief processing note, and retain the input; if only a technical sample check was completed, clearly state that real complex documents or in-host synchronization were not verified. No other sibling skill resources are needed; this skill contains all necessary references and scripts.