Explore document relationships in a Fux index using explain, graph, and path commands.
npx skills add https://github.com/arpitarya/fux --skill fux-graph-arpitarya
Please help me install this Agent Skill. Skill: fux-graph Source: https://github.com/arpitarya/fux/tree/main/.agents/skills/fux-graph Command: npx skills add https://github.com/arpitarya/fux --skill fux-graph-arpitarya
explain, graph, path) to answer relationship questions over a committed Fux index. ## Core Features & Use Cases - Outbound edge inspection: Use fux explain <doc> --json to list a document's outbound links, tags, supersessions, and code references, each with a reliability grade. - Neighbourhood exploration: Use fux graph "<query>" or fux graph --seed <doc> to walk the neighbourhood around query matches or named documents via a personalised random walk. - Route finding: Use fux path X Y --json to find the most reliable directed route between two documents, with reliability computed from edge grades and hop decay. - Use Case: A teammate asks "what superseded the storage decision record and what else depends on it?" — run fux explain on the record to see its edges, then fux path to trace how it connects to the runbook that replaced it. ## Quick Start Ask the agent to show what a specific document links to and how it relates to another document in the Fux index, and it will resolve the fux command and run the appropriate explain, graph, or path query with JSON output.High-intent search queries and answers about installing and using this skill.
Run fux explain <doc> --json to list the document's outbound edges — links, tags, supersessions, and code references — each with a reliability grade. Note that explain is outbound only; inbound edges require reading .fux/runtime/graph.json or the MCP fux_related tool.
Run fux path X Y --json, then fux path Y X --json since routes are directed. The output lists up to 10 routes sorted by reliability, computed as the product of edge grades halved per extra hop. An empty paths array means the documents are genuinely unconnected.
fux graph walks all edge kinds with unbounded hops and no hub damping, while ask's related list is a one-hop, ref-only, hub-damped neighbourhood of its own answers. Check ask's related list first, and use graph when you need other edge kinds or more hops.
An empty paths array with exit 0 means both documents exist in the index but no directed route connects them within the hop limit — this is a finding, not an error. Do not widen --hops to force a route; confirm both ends exist with fux explain first.
Grade 8 means the edge matched a file by basename alone, which can point at a same-named file elsewhere such as an archived copy. Verify the target before building any claim on a grade-8 edge; grade 10 edges are unambiguous resolutions.
All three graph verbs need the derived plane written by fux build into .fux/runtime/. Run fux build first, and rerun it after pulling commits or ingesting new documents, since the plane is not checked for currency.
sharpninjaIngest raw text into a GraphRAG knowledge graph and run graph-aware queries.
ktrysmtIdentify GitHub repositories and gather evidence with DeepWiki MCP.
collat-labsRetrieve LangGraph documentation pages and answer API usage questions.
islamu-ngoExplore repository structure and trace code relationships using a knowledge graph.