First readthe specific methods, parameters, and boundaries, then 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 needs bidirectional jumps between the meeting agenda and appendix within a PDF. First verify the input file, the scope of modifications approved by the user, and the target output. rect is the pt of the starting point from the top-left corner of the displayed page, not the bottom-left coordinate of the comparison report; it must be recalculated using the current text_find result or rendered image. Example coordinates must not be applied as-is to a real agenda; the target is the PDF physical page, not the printed page number.
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
Open the output separately and check the internal links from page 1 to page 3 and from page 3 to page 1; have an independent interpreter read the target and confirm that the hotspot covers the specified text; keep the original text and source summary.
Deliver a genuinely existing new output and a brief processing note, and preserve the input; if only a technical sample check was completed, clearly state 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.