Remove AI watermarks

Drive the remove-ai-watermarks CLI. Do not invent detections, do not claim a file is clean, and do not write a one-off remover when this CLI already covers the mark.

This skill must work in any coding harness and with weaker models. Follow the checklist. Trust scripts/probe.py over guesses about GPU, Python, or installers.

Scope

Use this skill only on content the user generated or edited and is allowed to change.

Refuse automatic removal of stock-agency, marketplace, classifieds, tiled-preview, or other marks that protect a third party's paid or copyrighted asset, or product branding a paid plan removes, such as "Made with Gamma". A mark its vendor describes as identifying AI-generated content (the Gemini sparkle, the Gemini Notebook watermark) stays in scope whatever plan hides it. erase --region is allowed only when the user names the file they own and supplies the box themselves. LLM text watermarks are out of scope: they live in word choice, not characters, so do not offer to strip characters from text.

Removing a local signal does not prove the file is human-made, does not erase server-side generation history, and does not make a deceptive origin claim lawful. If the user wants to present generated work as human-made, stop.

The project is research software provided without warranty; the user is responsible for lawful use. Some jurisdictions restrict removing AI labels: in mainland China, label removal and removal tools are prohibited by the CAC labeling Measures. Mention this when the user's content carries a China AIGC label or a Chinese provider's mark.

Workflow

Copy this checklist and check items off:

- [ ] 1. Scope is allowed
- [ ] 2. Probe the machine
- [ ] 3. Install if the CLI is missing or its pixel stack is
- [ ] 4. Identify first unless the user already named a removal
- [ ] 5. Run one command with -o
- [ ] 6. Report from the exit code and output path

1. Scope