Skip to content

po4yka/llm-wiki-skills / skills/llm-wiki-privacy-redactor

llm-wiki-privacy-redactor

Verified

Preview and plan redaction of private or sensitive content before publishing, exporting, or sending LLM-Wiki context to external models. Use for emails, tokens, internal URLs, phone numbers, private tags, and sensitive page metadata.

LLM-Wiki Privacy Redactor

Goal

Prevent private content from leaking through public exports, model-boundary payloads or shared reports.

When to use

  • Before exporting wiki pages, folders, or bundles to an external destination.
  • Before sending LLM-Wiki context across a model boundary to a third-party LLM.
  • When a page or raw source is tagged privacy: sensitive or marked internal.
  • When preparing a publishable report that may contain unreviewed generated claims.
  • When a redaction policy file exists and must be applied before publication.

Inputs

  • Target pages, folders or export bundle.
  • Redaction policy file if present.
  • Desired mode: preview-only or approved patch.
  • Publication or model-boundary target.

Procedure

1. Load policy

Read references/docs/security/redaction-policy.md and references/templates/redaction-policy.yml when available, and re-verify the policy file is the current version before applying it, since redaction rules can change between publications.

2. Classify content

Flag:

  • email addresses;
  • phone numbers;
  • internal URLs;
  • secret-like strings;
  • private tags;
  • pages with privacy: sensitive;
  • raw sources marked internal/sensitive;
  • unreviewed generated claims in publishable output.

3. Preview redactions

Run or recommend:

node scripts/redact-preview.mjs <path>

Show redaction candidates without modifying files.

4. Propose replacements

Use stable placeholders:

[REDACTED_EMAIL]
[REDACTED_INTERNAL_URL]
[REDACTED_SECRET]
[REDACTED_PHONE]

5. Apply only after approval

Apply changes only to an export copy unless the user explicitly asks to patch the source wiki.

Output

## Redaction summary

## Files inspected

## Findings by category

## Proposed redactions

## Export safety decision

## Review required

Safety gates

  • Do not print sensitive findings verbatim in final reports.
  • Do not mutate source wiki files by default.
  • Do not send sensitive content to external models without explicit approval.
  • Do not treat redaction as proof that publication is safe.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall