anonymize-paper

Anonymize Paper

Make a LaTeX submission genuinely double-blind — then undo it cleanly after acceptance. Anonymization leaks are documented desk-reject grounds (CHI and NeurIPS state this explicitly, including leaks in supplementary material and linked repos), and de-anonymization done by hand routinely leaves placeholder authors or dead anonymous.4open.science links in the published PDF. This skill runs the deep sweep in both directions and records every change so the reversal is mechanical, not archaeological.

When to use

• "Anonymize my paper for NeurIPS / CHI / ICML / KDD ..." / "blind this"
• "Did I leak my identity anywhere?" / "double-blind check" before submission
• "Rewrite my self-citations in third person"
• "My code/data links identify me — what do I do?"
• After acceptance: "de-anonymize", "restore the authors", "prepare the camera-ready author block"
• Called from tailor-to-venue (anonymization sweep step) or before preflight-check (final gate).

Inputs

1. The main .tex file (with \documentclass); \input/\include files are followed automatically.
2. The venue profile venues/conferences/<venue>-<year>.yml (schema in venues/schema.yml) — supplies the blind level (single/double/triple) and the cfp_url. No profile? Ask the user for the blind level or create a profile with parse-cfp.
3. Optional but recommended: the compiled PDF (metadata check), the supplementary directory, and the author/institution names to grep for.

Process — anonymize (submission)

1. Resolve the blind level, then re-verify it live — mandatory. Read the venue profile; fetch the cfp_url and confirm the blind level and the venue's anonymization policy wording (what counts as a violation, whether acknowledgments must be removed, whether anonymized artifact links are allowed). Single-blind venues (e.g. SIGSPATIAL) need no anonymization — tell the user and stop instead of mangling a fine paper.

2. Run the deep scan: