agentleFS
HybridAIOneHybridAIOne/hybridclaw/skills/distil-pii-redactor/SKILL.md

distil-pii-redactor

Skill159 starsChanged 6 months agoMITView on GitHub

Redact, anonymize, sanitize, or remove PII locally with Distil-PII and llama.cpp; keep personal data and secret values out of model context, logs, and chat.

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the user asks to redact, anonymize, sanitize, or remove PII or personal data from text.

    line 34
  2. Distinctive:

    Do not quote, summarize, or repeat raw PII in chat.

    line 40
  3. Distinctive:

    Prefer file-based input and output when the sensitive text is already in a file or attachment.

    line 41
  4. Distinctive:

    If the user asks for only the LLM or redaction output, do not narrate setup, server status, tool use, or validation details in the final …

    line 45
  5. Very specific:

    Do not use --show-entities in normal workflows.

    line 47
  6. Distinctive:

    Do not store raw PII in tracked files, shell history, long-lived notes, or logs.

    line 48
  7. Very specific:

    Do not convert raw PII into HybridClaw secrets.

    line 53
  8. Very specific:

    If llama-server is missing, install it with:

    line 58
  9. Distinctive:

    Start the local server:

    line 69
  10. Very specific:

    Use --show-entities only while testing the redactor, because it includes the original sensitive values:

    line 118
  11. Distinctive:

    Do not paste debug JSON back to the user unless they explicitly requested it and understand that it contains original PII.

    line 126

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Distil PII Redactor

Use this skill when the user asks to redact, anonymize, sanitize, or remove PII or personal data from text. It runs a local Distil-PII GGUF model through llama-server; raw text must not be sent to external APIs.

Privacy Rules

  • Do not quote, summarize, or repeat raw PII in chat.
  • Prefer file-based input and output when the sensitive text is already in a file or attachment.
  • Return only the redacted text unless the user is explicitly debugging the redactor itself.
  • If the user asks for only the LLM or redaction output, do not narrate setup, server status, tool use, or validation details in the final response.
  • Do not use --show-entities in normal workflows. It emits original values.
  • Do not store raw PII in tracked files, shell history, long-lived notes, or logs.
  • This skill declares no external credentials. If a downstream tool needs authentication, use that tool's HybridClaw secret_ref or gateway secret injection and pass only redacted text downstream.
  • Do not convert raw PII into HybridClaw secrets. Secret refs are for credentials and auth material, not a transport for user data.

Setup

If llama-server is missing, install it with:

hybridclaw skill install distil-pii-redactor llama-server

or install llama.cpp manually. This skill intentionally has no credentials: frontmatter because local inference does not need API keys; any future remote-provider variant must declare secret_ref credentials instead of reading raw environment variables.

Start the local server:

bash skills/distil-pii-redactor/scripts/setup.sh

The setup script stores the model under ~/.hybridclaw/distil-pii by default, downloads the public Distil-PII 1B GGUF model if missing, and starts llama-server on 127.0.0.1:8712.

Stop the server:

bash skills/distil-pii-redactor/scripts/stop.sh

Redaction Workflow

For files, keep raw input and redacted output on disk:

python3 skills/distil-pii-redactor/scripts/redact.py \
  --input-file sensitive.txt \
  --output-file redacted.txt

For stdin:

python3 skills/distil-pii-redactor/scripts/redact.py < sensitive.txt

For short text that is already in the conversation, pass it directly only when there is no lower-exposure path:

python3 skills/distil-pii-redactor/scripts/redact.py "text to redact"

The default output is only redacted_text, with sensitive spans replaced by tokens such as [PERSON], [EMAIL], [PHONE], [ADDRESS], [SSN], [CARD_LAST4:1234], and [IBAN_LAST4:1234].

The redactor refuses non-loopback --server-url values by default. Use --unsafe-allow-remote only for an explicitly trusted endpoint after the user accepts that raw text will leave the local machine.

Debug Output

Use --show-entities only while testing the redactor, because it includes the original sensitive values:

python3 skills/distil-pii-redactor/scripts/redact.py --show-entities \
  --input-file fixture.txt

Do not paste debug JSON back to the user unless they explicitly requested it and understand that it contains original PII.

Validation

Run:

python3 skills/skill-creator/scripts/quick_validate.py skills/distil-pii-redactor
python3 skills/distil-pii-redactor/scripts/redact.py --help
bash -n skills/distil-pii-redactor/scripts/setup.sh
bash -n skills/distil-pii-redactor/scripts/stop.sh

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.