Use `graphify-dotnet` to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and architecture snapshot generation. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 21 of 22 test cases with the skill, and 10 of 22 without it.
Without skill45%
With skill95%
Checks it passed that the model alone missed
Specifies .NET 10 SDK.
Recommends Ollama as the provider.
Uses graphify run with provider none.
and 18 more in the full report
12 fixed9 passed either way0 still failing1 broke
Pass-rate lift
+50 pp
Tokens
+21%
Agent turns
0%
Response time
-58%
Model gemini-3.6-flashMeasured 8/19/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
Before installing and running the graph extraction CLI tool, what .NET SDK version is required to be installed on the host machine?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies .NET 10 SDK.
Missed
Passed
case-20 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md157 lines3 files
graphify-dotnet
Trigger On
graphify, graphify run, graphify watch, graphify benchmark, or graphify config
generating graph.json, graph.html, graph.svg, graph.cypher, GRAPH_REPORT.md, obsidian/, or wiki/
building onboarding maps, architecture snapshots, or dependency-discovery artifacts from a repository
choosing between AST-only extraction and AI-enriched semantic extraction
pushing graph output into Neo4j, Obsidian, wiki docs, or CI artifacts
Workflow
Confirm the problem is structural discovery, architecture review, onboarding, or graph export. If the user only needs one symbol lookup, one bug fix, or one dependency trace, normal repo search and tests are cheaper than a full graph run.
Install and verify the tool before doing anything else: