What problem does it solve? Setting up and maintaining a Fux search index involves several verbs (setup, doctor, ingest, build) with strict preconditions, lock semantics, and commit rules; this Skill guides an agent through each job so the committed index in .fux/index/ stays valid, current, and byte-identical across clones. ## Core Features & Use Cases - Scaffold and configure: Run fux setup to write fux.toml, source lists, PII rules, and agent files, with controls like --no-agents and [agents] install to limit what is written. - Diagnose before acting: Parse fux doctor --json output, branch on the ok flag and per-row level, and map every failing check row to its documented fix without parsing free-text details. - Build and rebuild the index: Run fux ingest for delta or --full rebuilds, handle the write lock and stale locks, and use fux build to regenerate the derived accelerator that explain, graph, and path require. - Use Case: A teammate says CI fails because the index is stale. You add a workflow step that runs fux doctor, then fux ingest --no-accelerator --no-progress, and gates on git status --porcelain over .fux/index to prove the committed index matches the sources. ## Quick Start Ask the agent to run fux doctor with JSON output in this repository and fix whatever error-level rows it reports.