First readSpecific methods, parameters, and boundariesthen followstructured stepsto execute. The numeric 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 provides old and new PDFs and needs text changes listed and a difference report delivered. First verify the input files, the user-approved scope of changes, and the target output. Text comparison does not prove that images, vectors, complex reflow, and scanned content are completely identical; limit may truncate, so the total number of changes and the returned list must be checked, and exceeding the limit must not be treated as a complete review. The comparison rectangle uses PDF bottom-left coordinates and is not directly used as a link_add hotspot.
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 pass off a similar command as the real one.
Verification and delivery
The report clearly states the old value and the new value, the direction of the difference is correct, and unchanged content on the same page is not falsely reported; independently extract the report text for verification. The summaries of both the old and new sources remain unchanged.
Deliver the new output that actually exists and a brief processing note, and preserve 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.