anonymize-paper
From the author
Deep anonymization sweep for double-blind paper submissions, plus clean de-anonymization for camera-ready. Use when a researcher says "anonymize my paper", "double-blind check", "blind this submission", "remove author names", "did I leak my identity" — or, after acceptance, "de-anonymize" / "restore authors for camera-ready". Sweeps the whole leak surface, \author/\affiliation/\email/\orcid/\thanks, acknowledgments and grant numbers, hyperref pdfauthor and compiled-PDF metadata, first-person self-citations (rewritten to third person), GitHub/dataset/homepage links vs anonymized mirrors, LaTeX comments, .bib annotations, home-directory paths, and supplementary material (.git dirs, notebooks, LICENSE/AUTHORS files). Bundles a stdlib-only scanner (scan_anonymization.py, check ids shared with preflight-check) and a reversible-edit workflow (toggle + manifest) so every change is cleanly undone at camera-ready. Advisory only; never submits anything.
Install
npx skills add ShaishavMaisuria/research-paper-lifecycle-skills --skill anonymize-paper -a claude-code
Installs to .claude/skills/anonymize-paper/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 76
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- cav-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing an accepted CAV (Computer Aided Verification) paper for its Springer LNCS open-access camera-ready, covering de-anonymization for the previously double-blind categories, the LNCS llncs template and Springer metadata (ORCID, author order, running heads), the copyright/open-access forms, integrating reviewer-required changes without scope creep, permanentizing artifact links, and the AEC badge handoff.Science★ 1.3K
- preflight-checkShaishavMaisuria/research-paper-lifecycle-skillsDeterministic desk-reject preflight linter for LaTeX paper submissions. Use it when a researcher asks "is my paper ready to submit", or mentions preflight, desk reject, submission check, page limit, anonymization, double-blind, missing checklist, or format/template compliance for a conference (NeurIPS, ICML, CHI, SIGSPATIAL, SIGMOD, ICDE, CVPR, LNCS...). Lints the .tex source against a machine-readable venue profile for documentclass and style-file options, margin/template tampering (geometry, savetrees, spacing hacks), anonymization leaks (author block, acknowledgments, repo links, first-person self-citations, \thanks, pdfauthor), required sections (NeurIPS checklist, ICML impact statement, AI-use acknowledgement, COI, CCS concepts/keywords), abstract length, keywords format, and page-limit risk. Every finding is reported with file:line. Runs bundled stdlib-only Python scripts; advisory only, never submits anything.Science★ 58
- prepare-camera-readyShaishavMaisuria/research-paper-lifecycle-skillsStep-by-step camera-ready prep for accepted papers — the error-prone final stage before publication. Use when a researcher says "camera-ready", "final version", or "my paper got accepted, now what", or mentions ACM eRights / rights form / TAPS / ORCID / DOI block, IEEE PDF eXpress / conference ID / eCF copyright form / Xplore, OpenReview final upload, de-anonymization, or extra camera-ready pages. Resolves the venue's rail from a machine-readable profile and walks it end to end across ACM eRights, ORCID, rights/DOI block, TAPS source upload, IEEE PDF eXpress, conference IDs, file naming, eCF exact-title match, registration/no-show, NeurIPS-style [final] recompile, and OpenReview upload. Generates an ordered checklist with deadlines and +page rules, and lints the final .tex for leftover anonymization and missing rights blocks via bundled stdlib-only scripts. Advisory — it prepares, explains, and lints, but never completes a form or submits anything.Documents★ 58
- hri-camera-readybrycewang-stanford/Awesome-Journal-SkillsUse when preparing the camera-ready of an accepted ACM/IEEE HRI paper — de-anonymizing systematically, completing ACM+IEEE dual-publication metadata (CCS concepts, ORCID, rights/eRights form), delivering every rebuttal promise within the 8-page budget, finalizing the video and de-anonymized archive, and passing production checks.Media★ 1.3K
- anonglebis/claude-skillsDe-identify a session transcript (file or folder) by redacting PII LOCALLY before any sharing or cloud use. Produces a redacted GREEN copy with unique reserved-sentinel placeholders ([CONFIDE_PERSON_0001], [CONFIDE_EMAIL_0001], [CONFIDE_DATE_0002]...) plus a counts-only stats summary, and a local secret <name>.map.json (0600, gitignored) that enables confide:rehydrate to restore real values after a cloud analysis. Use when the user says "anonymize this transcript", "redact PII", "de-identify session", "make safe to share", "strip personal data", "anonymize notes before sending to an LLM", or points at a transcript/folder that should be scrubbed. Local-only by default — raw text never leaves the machine; the map is the only artifact with originals and stays local; nothing printed is PII; human review is still required before sharing.Engineering★ 403
- anti-slopAgriciDaniel/anti-slopRouter for the anti-slop toolkit. Use when someone asks to review, clean, de-slop, humanize, or quality-check prose, documentation, code, commit messages, PR descriptions, or agent output, or asks whether some writing "sounds like AI". Also use for verifying citations, DOIs, links and imported package names, for stripping vendor residue markers such as oaicite or cite spans, and for auditing padding, filler, puffery, vague attribution and hollow analysis. Explains the three layers (deterministic scanners, structural procedures, evidence-tiered soft signals) and picks the right leaf skill: slop-review for read-only findings, slop-rewrite for repair, slop-code for code and docs, slop-verify for citations, links and packages. Never produces an authorship verdict and never treats a stylistic marker as proof of anything. Use this hub only when the surface or the operation is unclear; otherwise invoke the leaf skill directly.Writing★ 65
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in