First readSpecific methods, parameters and boundaries, then follow thestructured stepsto execute. The values, file names and headings 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 needs a long report to allow quick jumps by chapter and appendix. First verify the input file, the scope of modifications approved by the user and the target output. Chapter page numbers must be confirmed from the current PDF and the user's table of contents. parent is the bookmark location path, not a page number; if existing bookmarks are present, inventory them first and do not blindly append duplicate-named entries. This is not automatic heading recognition or accessibility certification.
Stay within 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
Open the output separately and use bookmark_list to verify the Report→Findings hierarchy and the 1/2/3 target pages; use an independent PDF interpreter to read the table of contents, and confirm the original page text and source file summary are unchanged.
Deliver the actually existing new output and a brief processing note, keeping the input; if only a technical sample check was completed, state clearly that a real complex document or in-host synchronization was not verified. No other sibling skill resources are needed; this skill contains all necessary references and scripts.