fux-config

Diagnose and explain Fux configuration files including fux.toml, tune.toml, and output.toml.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/arpitarya/fux --skill fux-config-arpitarya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fux-config
Source: https://github.com/arpitarya/fux/tree/main/.agents/skills/fux-config
Command: npx skills add https://github.com/arpitarya/fux --skill fux-config-arpitarya

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about fux-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change Fux ranking weights like BM25F parameters?▼

Edit the [bm25f] table in .fux/tune.toml, which holds k1, b, and field weights for body, heading, title, path, and ctx. Run fux tune to print engine defaults, and compare per-query ranks before and after the edit rather than trusting average scores.

How do I always show the confidence band in fux ask results?▼

Set band = true under the [cli] table in .fux/output.toml. CLI flags override config values, and --no-output-config bypasses the file entirely when you need engine defaults.

Why does fux.toml fail to load with an unknown key error?▼

Fux refuses any unknown key by name and lists what is legal at that level. Common causes are ranking or decode keys that moved to .fux/tune.toml, or typos like metta instead of meta; the error message names the new home.

Does a working fux ask prove my fux.toml is valid?▼

No. fux ask and fux find keep answering on a fux.toml that fux ingest refuses, so a successful query proves nothing. Check the fux.toml loads row in fux doctor --json instead.

What is the difference between ttl, update, and fetch_at_answer in fux.toml?▼

ttl sets how long a URL citation is considered fresh at ask time, update = "never" stops re-fetching for the index, and fetch_at_answer = false keeps fux answer fully offline by verifying against retained bytes in .fux/acquired/.

When should I avoid editing Fux config files?▼

Avoid edits unless a human explicitly requested the change, because all config files are committed and affect every teammate, CI job, and agent. Never redirect fux tune or fux output over an existing file, since they print engine defaults and would erase repo-specific choices.