First readspecific methods, parameters, and boundaries, then followstructured 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 to mark a version on specified review pages while preserving other pages. First verify the input file, the modification scope approved by the user, and the target output. A watermark is not redaction, access control, or a signature; a watermark must not be used as a way to delete the original content. replace=false preserves existing watermarks; before repeated execution, first inspect the current copy, and do not unconditionally overprint.
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
Output visible REVIEW ONLY on pages 1 and 3, with no watermark on page 2 and unchanged rendered pixels; the original text on each page remains, the original PDF summary remains unchanged, and check that the watermark does not affect reading.
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 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.