Generates doc2query enrichment questions for documents in a Fux search corpus.
npx skills add https://github.com/arpitarya/fux --skill fux-enrich-arpitarya
Please help me install this Agent Skill. Skill: fux-enrich Source: https://github.com/arpitarya/fux/tree/main/.agents/skills/fux-enrich Command: npx skills add https://github.com/arpitarya/fux --skill fux-enrich-arpitarya
.fux/enrich/<sha>.md files that are committed to git and indexed as searchable context. - Plan-driven workflow: Uses fux enrich --plan to get the exact worklist, sha, and chunk count, then re-verifies the sha immediately before writing to avoid stale enrichment. - Retrieval validation: Every question is checked with fux enrich --check, which runs each question as a real search and refuses the file if the question does not place its own document in the top 3. - Use Case: A user asks to "enrich the ranking SR". The Skill runs the plan, reads records/0111_ranking.md, writes questions like "How does fux decide which result comes first?", validates them, and the document becomes findable by searcher vocabulary. ## Quick Start Enrich the document records/0111_ranking.md in my Fux corpus so it can be found by questions it does not literally answer.High-intent search queries and answers about installing and using this skill.
Run fux enrich --plan with the document path to get its sha and chunk count, read the document, then write five to ten searcher-vocabulary questions into .fux/enrich/<sha>.md with the required frontmatter. Validate the result with fux enrich --check before finishing.
Doc2query is a technique that generates questions a document could answer and indexes them as extra searchable text, so the document matches queries using words it never contains. Fux applies the doc2query-- filter, refusing any generated question that does not retrieve its own document in the top 3 results.
The check runs every question as a real search with the title and ctx fields zeroed, and refuses the file if a question fails to place its own document in the top 3. It also refuses files missing required frontmatter keys or containing patterns matched by rules in .fux/pii.toml.
STALE means the document changed after it was last enriched, so the recorded sha no longer matches. Treat it like a missing enrichment: re-run the plan, write a fresh file under the new sha, and do not edit the old file.
Only run it when a human explicitly asks to enrich, re-enrich, or fill in enrichment, because the generated files are committed to git and change search ranking. Never run it as a side effect of another task, and ask before proceeding when a plan covers multiple documents without a named scope.
Unique-AGSearch the Unique knowledge base with scoped queries and metadata filters.
allanninalAnalyze git commits against security audit findings to verify remediation.
jcafeitosaPromote provisional research notes into stable canonical articles with supersession audit trails.
zilliztechConvert text into embeddings and retrieve semantically similar items from a vector store.