noirdoclisted

# noirdoc — privacy-preserving document workflow This skill lets you work with sensitive local documents without pulling raw PII into your context. It orchestrates the `noirdoc` CLI: redact on the way in, reveal on the way out, so the user sees real names in your final output while your working context only holds placeholders like `<<PERSON_1>>` and `<<IBAN_CODE_1>>`. ## When this applies **Use this skill when:** - The user asks you to read / summarize / translate / analyze / edit a document under `./incoming/`, `./clients/`, `./contracts/`, or any file matching `*.contract.*`, `*.nda.*`, `*.patient.*`. - A `PreToolUse` block comes back with "noirdoc-protected" in the message. - The user says anything about "redact", "pseudonymize", "DSGVO", "PII", "GDPR", "anonymize names", "noirdoc", or German legal/HR/medical documents. - The user drops a PDF/DOCX/XLSX of a contract, employment agreement, invoice, or similar into the workspace and asks you to work with it. **Don't use this skill when:** - The user's question is purely about code, configuration, or non-document files (source files, JSON configs that are clearly not PII). - The file is already a redacted copy (look for `.noirdoc/cache/` prefix, or placeholders like `<<PERSON_1>>` in a preview). - The user has explicitly told you the document contains no personal data and asked you to skip redaction — respect that, don't argue. ## First-run setup Before anything else, check whether this workspace is already set up: `