skill-graph
Skill2 starsChanged 6 months agoMITView on GitHub
Use the local skill-graph CLI to resolve tasks into graph-based skill context, load shallow context first, and expand full skills only when needed.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Vix0007/vixero-skillstheir own version, first seen Apr 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Vix0007/vixero-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when a task could benefit from specialized agent skills, especially work involving frontend polish, testing, documentation, …
- Distinctive: line 32
Ask before installing any remote skill.
- Distinctive: line 53
Prefer installed local skills when they are good enough.
- Distinctive: line 54
Use ancestors at shallow depth.
- Distinctive: line 55
Use direct matches at the deepest useful depth allowed by budget.
- Distinctive: line 56
Keep complements on the frontier until the task requires them.
- Distinctive: line 57
Treat conflicts as warnings that need human review before loading both skills at full depth.
- Distinctive: line 58
Treat inferred edge suggestions as review items, not active resolver policy.
- Distinctive: line 59
Never install remote skills without explicit user approval.
- Distinctive: line 60
Treat remote-cache results as metadata only until the user approves an install.
- Distinctive: line 61
Do not enable any embedding provider that uploads local task, repository, or private skill text without explicit human approval.
- Very specific: line 62
Do not pass --trust-remote-code unless the user explicitly accepts local execution of model repository code.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
skill-graph
Use this skill when a task could benefit from specialized agent skills, especially work involving frontend polish, testing, documentation, deployment, security review, performance, or framework-specific implementation.
Runtime Loop
Resolve the task before specialized work:
skill-graph resolve "<task>" --format markdown- Load the selected shallow context first.
- Inspect the task and repository.
Expand only nodes justified by new evidence:
skill-graph expand <node-id> --depth summaryExpand to full context only when the summary is insufficient:
skill-graph expand <node-id> --depth full- Ask before installing any remote skill.
- At the end, report which nodes were loaded and which frontier nodes were skipped.
Commands
skill-graph index: scan local skill roots and write.skill-graph/index.json.skill-graph index --skills-sh-query "<query>": include not-installed skills.sh candidates in the graph for the current domain.skill-graph remote-cache "<query>": cache skills.sh candidates and show approval-required install commands.skill-graph embeddings index: build a local semantic embedding index. Use the defaultqwen3-localprovider only when local Python dependencies and model storage are acceptable; use--provider deterministicfor tests and demos.skill-graph embeddings index --trust-remote-code: allow model repository code execution only after explicit human review of the model source.skill-graph embeddings info: show the saved local embedding provider, model, dimensions, and vector count.skill-graph edges suggest: propose inferred edges from embedding similarity for human review; do not treat proposed edges as canonical.skill-graph search "<query>": search the local graph with BM25 by default; use--strategy lexicalfor baseline comparison,--strategy semanticafter embeddings exist, or--strategy hybridfor BM25 plus lexical plus semantic fusion.skill-graph resolve "<task>": return selected nodes, context depths, frontier nodes, conflicts, missing nodes, scoring provider provenance, and reasons. Hybrid resolution includes semantic results only when a local embedding index already exists.skill-graph expand <node-id> --depth <depth>: load deeper context for one node.skill-graph context: show context layers loaded in the current workspace.skill-graph explain --last: explain the last resolution path.skill-graph install <node-id>: show the exact dry-run install command for a remote node when available.
Operating Rules
- Prefer installed local skills when they are good enough.
- Use ancestors at shallow depth.
- Use direct matches at the deepest useful depth allowed by budget.
- Keep complements on the frontier until the task requires them.
- Treat conflicts as warnings that need human review before loading both skills at full depth.
- Treat inferred edge suggestions as review items, not active resolver policy.
- Never install remote skills without explicit user approval.
- Treat remote-cache results as metadata only until the user approves an install.
- Do not enable any embedding provider that uploads local task, repository, or private skill text without explicit human approval.
- Do not pass
--trust-remote-codeunless the user explicitly accepts local execution of model repository code.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

