Install any skill in seconds. Free to start, no credit card required.
Get Started Free →quinnaho/claudemap-runtime
Internal ClaudeMap runtime for turning a repository into a live architecture map and driving that map during walkthroughs. Prefer the public commands in .claude/commands for normal use.
Passed 10 of 15 test cases with the skill, and 5 of 15 without it.
and 13 more in the full report
9 fixed5 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to run the architecture snapshot tool specifically against the path `/opt/services/checkout-api`. How should the target root argument be passed to the execution tool?
| Checked | Without skill | With skill |
|---|---|---|
| passes the provided directory argument to `${CLAUDE_SKILL_DIR}/skill/commands/snapshot.js`. | Missed | Passed |
| uses the explicit argument path instead of the current working directory. | Missed | Passed |
The instructions your model reads when the skill loads.
ClaudeMap is a repo-to-architecture-map workflow.
High-level model:
@claudemap-architect to turn that snapshot into a detailed, human-legible graphPublic commands:
/setup-claudemap: build or rebuild the map for the current repository/open-claudemap: reopen the existing UI without rebuilding/create-map: create or refresh a scoped subsystem map from the current root graph/refresh: update the graph after code changes/explain: run a guided walkthrough through the live map/show: direct the live map for highlights, focus, presentation, and flowsIf this skill is invoked directly, default to the setup workflow.
Target repository:
$ARGUMENTS as the project root.Execution rules:
${CLAUDE_SKILL_DIR}.${CLAUDE_SKILL_DIR}/skill/commands/snapshot.js for the target project root.${CLAUDE_SKILL_DIR}/skill/prompts/enrichment.txt.@claudemap-architect subagent explicitly. Give it:
${CLAUDE_SKILL_DIR}/tmp/claudemap-enrichment.json. Do not run the setup JS command until after this file has been written with non-empty valid graph JSON. Do not run setup in parallel with the subagent call.${CLAUDE_SKILL_DIR}/skill/commands/setup-claudemap.js for the target project root with --enrichment-file ${CLAUDE_SKILL_DIR}/tmp/claudemap-enrichment.json. The setup command is strict: if the file is missing, empty, or unparseable it will exit non-zero and refuse to render a heuristic graph. Do not retry setup without fixing the enrichment file first.--force-refresh only when the user explicitly asks for a fresh rebuild.--enrichment-file — that would render a heuristic graph and pollute the cache. The user should rerun /setup-claudemap once the architect issue is resolved.test cases passed, vs 5 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.