wiki-graph-query
Skill4 starsChanged 6 months agoApache-2.0View on GitHub
SOP wrapping vault_query_graph — traverse knowledge graph from a node to explore its neighborhood and context.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- yogsoth-ai/knowledge-structuringword for word, first seen May 18, 2026
Other versions1 project uses a version of this.
Word for word · 1
- yogsoth-ai/knowledge-structuring★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository7 other files it gives its agents.
- knowledge-compilationSkill
- vault-maintenanceSkill
- wiki-add-edgeSkill
- wiki-compile-pageSkill
- wiki-ingest-sourceSkill
- wiki-lint-fixSkill
- wiki-searchSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 16
Verify the file exists before calling vault_query_graph.
- Very specific: line 35
Call vault_query_graph with node, direction, and optional filters
≈ “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
Wiki Graph Query
Explore the neighborhood of a node in the knowledge graph. Used for understanding context before updates, finding connection opportunities, and identifying orphans.
HARD-GATE
<HARD-GATE>
Node path must reference an existing file in the vault.
Verify the file exists before calling vault_query_graph.
</HARD-GATE>Tool
vault_query_graph
Parameters
| Param | Required | Description |
| node | yes | Starting node path (e.g., "concepts/attention.md") |
| direction | yes | Traversal direction: "in", "out", or "both" |
| edge_type | no | Filter by edge type |
| depth | no | Traversal depth (default 1, max 3) |
Protocol
- Confirm node file exists in vault
- Call
vault_query_graphwith node, direction, and optional filters - Analyze subgraph: identify clusters, orphan branches, missing connections
- Return subgraph data to calling tactic
Yield
Returns: { nodes_found: number, edges_found: number, subgraph: object }
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.