Analyze a Karpathy-pattern LLM wiki knowledge base and generate an interactive knowledge graph with entity extraction, implicit relationships, and topic clustering.
SkillScore73Maintained
Automatic
◆Knowledge Management pack
Last verified 8/7/2026
What it changes
Passed 13 of 18 test cases with the skill, and 6 of 18 without it.
Without skill32%
With skill73%
Checks it passed that the model alone missed
Sets graph kind property to knowledge
Includes analyzedFiles count in meta.json
Includes version string set to 1.0.0 in meta.json
and 9 more in the full report
10 fixed6 passed either way5 still failing1 broke
Pass-rate lift
+41 pp
Tokens
+16%
Agent turns
0%
Response time
-62%
Model gemini-3.6-flashMeasured 8/7/2026v116 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Before writing the final `knowledge-graph.json` file in Phase 5, what validation check must be performed on node relationships?
What was checked, without and with the skill
Checked
Without skill
With skill
Removes any edges where the source or target ID does not match an existing node
Missed
Passed
case-16 · gemini-3.6-flash · 8/7/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md131 linessingle file
/understand-knowledge
Analyzes a Karpathy-pattern LLM wiki — a three-layer knowledge base with raw sources, wiki markdown, and a schema file — and produces an interactive knowledge graph dashboard.
Raw sources — immutable source documents (articles, papers, data files)
Wiki — LLM-generated markdown files with wikilinks ([[target]] syntax)
Schema — CLAUDE.md, AGENTS.md, or similar configuration file
index.md — content catalog organized by categories
log.md — chronological operation log
Detection signals: has index.md + multiple .md files with wikilinks. May have raw/ directory and schema file.
Instructions
Phase 1: DETECT
Determine the target directory:
If the user provided a path argument, use that
Otherwise, use the current working directory
Resolve the data directory $UA_DIR once, and reuse it for every read and write below: UA_DIR="<TARGET_DIR>/$([ -d "<TARGET_DIR>/.understand-anything" ] && echo .understand-anything || echo .ua)" — this selects the legacy .understand-anything/ when it already exists, otherwise the new .ua/.
Run the format detection script bundled with this skill: