fux-inspect

Inspect a Fux search index to report boilerplate, duplicates, unfindable documents, and graph orphans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams maintaining a Fux search index cannot tell whether the index is healthy — which documents no query can reach, which words appear on everything, or whether the corpus is full of near-duplicates. This Skill reads the shape of a Fux index with fux inspect and turns its report into actionable findings. ## Core Features & Use Cases - Index health checks: Reads the checks array first — unreachable share, boilerplate share, near-duplicate share, and the descriptive findable share — with provisional floors reported as signals, never failures. - Corpus diagnostics: Surfaces boilerplate terms, template families, near-duplicate pairs, undecodable or unreadable documents, graph orphans and hubs, and vocabulary statistics like Zipf slope and distinct-term percentiles. - Lever mapping without applying it: Every finding names its remedy (stopwords, .fuxignore, fux enrich, decoders) but the Skill is strictly read-only and offline — it proposes commands and never runs them. - Use Case: When a user asks "why can't fux find this document" or "is our index any good", run fux inspect --json, read findability.unfindable and the counts beside capped lists, and report the findings with their levers. ## Quick Start Ask the assistant to run fux inspect on this repository and summarize whether the index is healthy, listing any unfindable or duplicate documents.

Frequently Asked Questions about fux-inspect

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

FAQPage Schema
How do I check if my Fux search index is healthy?▼

Run fux inspect --json and read the checks array first: unreachable share, boilerplate share, and near-duplicate share carry provisional floors, while findable share is descriptive only. Note that fux inspect exits 0 regardless of findings, so exit code is not a health signal.

Why can't fux find a specific document?▼

Check findability.unfindable and lengths.shortest in the fux inspect report — documents with no distinctive term cannot be selected by any query. The printed levers are fux enrich, fux correct, or fixing the source document.

How do I find duplicate documents in a Fux index?▼

Read duplication.near_duplicates and duplication.families from the inspect report, which lists pairs at Jaccard similarity of 0.80 or higher. Use duplication.pair_count for the true total since the list is capped by the --top flag.

Does fux inspect modify the index or fetch remote documents?▼

No. fux inspect is read-only and offline — it writes only to the gitignored .fux/runtime/inspect/ directory and never fetches URL documents. It proposes remediation levers but never applies them.

What are the limitations of fux inspect?▼

It requires a committed index and runs only in Python — there is no npx fux inspect. Words come from re-tokenizing local sources, so documents whose bytes are not on disk appear as unnamed hashes, and named lists are truncated by --top while counts are not.