Design and extend markdown skill graphs made of index notes, MOCs, and atomic linked nodes. Use when a domain is too deep for one SKILL.md, when the user wants a wiki-linked knowledge system, or when you need to separate stable methodology from live operational data.
Use this skill to turn one oversized skill or knowledge dump into a graph of small markdown notes that an agent can traverse progressively. The default path is:
index -> MOC -> node -> section
Most routing decisions should happen before reading full files.
Use it when:
SKILL.mdDefine the graph boundary. Decide what the graph should answer, what its main entrypoint is, and what stays out of scope.
Separate stable knowledge from live state. Put methods, heuristics, claims, decisions, and synthesized patterns in markdown. Put volatile facts, runtime state, provenance chains, metrics, and join-heavy relations in a typed store.
Create the entrypoint first. Start with one index note that names the main clusters and points attention.
Add MOCs only when a topic is large enough. Use MOCs to orient the reader. Do not use them as giant link dumps.
Write atomic nodes. Each node should hold one complete thought, method, tradeoff, or claim.
Use links inside prose. A wiki link should explain why the next note matters, not just prove that it exists.
Encode trust and freshness. Mark note type, state the source of truth, and make uncertainty explicit when the graph is incomplete.
Keep traversal cheap. Prefer one or two hops from the entrypoint over deep hidden chains.
Read these files as needed:
references/templates.md for entrypoint, MOC, and node templatesreferences/patterns.md for traversal rules, note types, and repo layoutsreferences/anti-patterns.md when the graph feels too big, too flat, or too stalereferences/hybrid-architecture.md when the markdown versus database boundary is unclearreferences/decision-guide.md when the main question is whether a graph is needed at allreferences/migration-playbook.md when splitting one oversized skill into a graphreferences/review-checklist.md when checking whether the graph is ready to usereferences/maintenance-checklist.md when the graph is starting to driftreferences/naming-conventions.md when note and file names are getting muddyreferences/example-graph/knowledge-work.md for a small working examplereferences/example-graph-business-ops/operations-knowledge.md for a business-operations exampleWhen building a graph for a user: