Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agenticnotetaking/graph
Interactive knowledge graph analysis. Routes natural language questions to graph scripts, interprets results in domain vocabulary, and suggests concrete actions.
Passed 6 of 14 test cases with the skill, and 4 of 14 without it.
and 6 more in the full report
8 fixed4 passed either way11 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When reporting raw graph metrics, triangle pairs, or isolated clusters, what rule governs how structural findings must be presented to the user?
| Checked | Without skill | With skill |
|---|---|---|
| Requires accompanying domain context descriptions rather than dumping raw data. | Passed | Passed |
| Demands actionable next step recommendations for every reported finding. | Missed | Passed |
The instructions your model reads when the skill loads.
Read these files to configure domain-specific behavior:
ops/derivation-manifest.md — vocabulary mapping, platform hints
vocabulary.notes for the notes folder namevocabulary.note / vocabulary.note_plural for note type referencesvocabulary.topic_map / vocabulary.topic_map_plural for MOC referencesvocabulary.cmd_reflect for connection-finding command namevocabulary.cmd_reweave for backward-pass command nameops/config.yaml — for graph thresholds (MOC size limits, orphan thresholds)
If no derivation file exists, use universal terms (notes, MOCs, etc.).
Target: $ARGUMENTS
Parse the operation from arguments:
START NOW. Route to the appropriate operation.
The graph IS the knowledge. This skill makes it visible.
Individual {vocabulary.note_plural} are valuable, but their connections create compound value. /graph reveals the structural properties of those connections — where the graph is dense, where it is sparse, where it is fragile, and where synthesis opportunities hide.
Every operation produces two things: findings (what the analysis reveals) and actions (what to do about it). Never dump raw data. Always interpret results with {vocabulary.note} descriptions and domain context. Always suggest specific next steps.
test cases passed, vs 4 / 14 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.