Diagnose and manage PII redaction rules in .fux/pii.toml for the fux search index.
npx skills add https://github.com/arpitarya/fux --skill fux-pii-arpitarya
Please help me install this Agent Skill. Skill: fux-pii Source: https://github.com/arpitarya/fux/tree/main/.agents/skills/fux-pii Command: npx skills add https://github.com/arpitarya/fux --skill fux-pii-arpitarya
fux answer can quote values that fux find cannot find. - Write and validate rules: Learn the TOML rule syntax (regex pattern, capture group, luhn/verhoeff checksum validation, flags) and which rule shapes are refused at load time. - Probe before committing: Run a scratch probe script against git-tracked files to see exactly what a candidate rule would redact, printing only location, length, and a hash — never the matched value. - Use Case: A teammate reports that order numbers disappeared from search results. Use this Skill to identify the over-broad shape-only rule, probe a narrowed pattern with a checksum validator, and re-ingest the index safely. ## Quick Start Ask the assistant to explain why fux reports that .fux/pii.toml is missing and what to do about it.High-intent search queries and answers about installing and using this skill.
Fux refuses to run without .fux/pii.toml because the file is committed policy deciding which values ship inside the shared index. Running `fux setup` writes a starter file while keeping existing files; never delete or empty the file to bypass the error.
Probe the candidate rule against git-tracked files with a scratch script using fux's own parser, narrow it until only intended values match, append it to .fux/pii.toml, verify with `fux doctor --json`, then run `fux ingest` to re-extract all documents.
That is by design, not a redaction failure. The committed index stores redacted text, while `fux answer` reads quotes directly from the source document under the reader's own access, so raw values can appear in answers.
Narrow the pattern with anchors, required separators, or lookarounds, or add a checksum validator like `validate = "luhn"`. Probe the revised rule first, since a checksum still passes roughly one random digit run in ten.
Document paths are never redacted because they address the record; ingest prints a note and you must rename or .fuxignore the file. URL documents are re-redacted only when re-fetched, so run `fux ingest --refetch-all` after a rule change.
aiappsgbbBuild Azure AI Search Knowledge Agents for citation-backed multi-hop retrieval.
JeromyJSmithMaintain DDC skill indexes in Qdrant and ingest BOQ data into IFC elements.
DisentinelDebug Grafema enrichment failures caused by edge type mismatches.
moyupeng0422Redact sensitive information from DOCX files using regex-based rules.