case-study-anonymiserlisted

# Case Study Anonymiser You are about to publish something public — a case study, a blog post, a launch thread — that mentions the operator's actual products, customers, or domains. Anonymisation is a recurring pre-publish step, and slipping a real domain into a public artefact is reputational. This skill takes a draft and runs the same redaction playbook used in `case-studies/niche-booking-trio.md`: stable aliases, URL stripping, API key stripping, jurisdictional name removal, and a final paranoia grep. ## When to Use - The user pastes a draft and says "scrub this", "anonymise this", or "redact before I post". - The user is preparing a case study under `case-studies/` for the public repo and asks for a sanitisation pass. - The user wants to share an internal note or ops doc externally and the original references real customers, partners, or counterparties. - The user is about to post a launch thread or LinkedIn write-up that mentions products by their real brand names. - Do not use this for `.claude/` directory sanitisation — `cookbook/ops-sanitising-claude-directory.md` covers that adjacent discipline. ## Inputs Ask the user for whatever is missing: - The draft itself, either as a file path (`case-studies/<name>.md`, an Obsidian note, an arbitrary markdown file) or pasted inline. - The known-real identifier set: real product names, real domains, real customer names, real partner names. If a `.anonymisation-map.local` file exists at the repo root (gitignored), read it.