What problem does it solve? Fux repositories carry several committed TOML configuration files whose keys interact in non-obvious ways, and a wrong edit changes ranking and output for every teammate, CI job, and agent. This Skill maps each question to the right file, explains every key and its precedence, and diagnoses validation errors without risking unintended edits. ## Core Features & Use Cases - File ownership mapping: Routes each question to the correct file — fux.toml for sources and URL policy, .fux/tune.toml for ranking and index limits, .fux/output.toml for display, and .fux/pii.toml for redaction. - Key reference and precedence: Documents every key with defaults, which verbs read it, and the full CLI-flag-to-config precedence chain for output settings. - Error diagnosis: Translates loader errors like unknown keys, moved tables, and missing max_parallel into concrete fixes, using fux doctor --json as the fastest check. - Honest tuning evaluation: Provides a per-query, rank-based before/after comparison procedure so tuning changes are judged on written expectations rather than averages. - Use Case: A user asks why fux.toml fails to load after adding a ranking key; the Skill identifies that ranking keys moved to .fux/tune.toml and gives the exact migration. ## Quick Start Ask the assistant to explain what a specific key in fux.toml or .fux/tune.toml does, or to diagnose why a Fux config file fails to load.