CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup-codemap-cli

Guide for setup Codemap CLI for intelligent codebase visualization and navigation

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/mcp/skills/setup-codemap-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete commands and config, and the nine-step workflow is clearly sequenced with verification steps. Its main weaknesses are some repeated caveats and large inline config blocks that could be split into reference files for better progressive disclosure.

Suggestions

Consolidate the repeated 'if default branch is not main' caveat into a single note referenced once instead of repeating it in steps 6 and 9.

Move the full hooks JSON example and the complete CLAUDE.md template into reference files (e.g. references/claude-template.md, references/hooks.json) and link to them from SKILL.md to improve progressive disclosure.

Add brief error-recovery guidance for the verification steps (e.g., what to check if 'codemap .' fails after install).

DimensionReasoningScore

Conciseness

Mostly concrete with little concept over-explanation, but the 'default branch is not main' caveat is repeated across steps 6 and 9, and the full 60+ line hooks JSON duplicates the Available Hooks table, so it could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready commands and config throughout (brew/scoop install, codemap invocations, exact CLAUDE.md content, exact settings.json hooks), covering the common cases comprehensively.

5 / 5

Workflow Clarity

Nine clearly numbered steps with verification checkpoints (step 5 verify install, step 8 test); the operations are non-destructive setup so the absence of a validate-fix-retry loop is acceptable, though no explicit error-recovery guidance is given.

4 / 5

Progressive Disclosure

Well-sectioned single file, but at ~230 lines the full CLAUDE.md template and the large complete-hooks JSON example are content that could live in reference files and is inlined; no bundle files exist to offload it.

3 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies the target tool and its purpose but omits any explicit 'Use when...' trigger guidance, which limits completeness and trigger-term quality. It is reasonably distinct thanks to the named tool, yet would benefit from concrete trigger phrases.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user wants to install or configure Codemap CLI for codebase navigation').

Drop the vague qualifier 'intelligent' and replace it with another concrete capability to raise specificity.

Include common natural trigger terms or synonyms users might say (e.g., 'code map', 'codebase tree', 'dependency visualization').

DimensionReasoningScore

Specificity

Names the domain ('Codemap CLI') and a couple of concrete capabilities ('codebase visualization and navigation'), but the only action stated is 'setup', so coverage is not comprehensive; 'intelligent' is mild fluff.

3 / 5

Completeness

Has a clear 'what' (guide to set up Codemap CLI for visualization/navigation) but no 'when' clause — there is no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant keywords ('Codemap CLI', 'codebase visualization', 'navigation', 'setup') but misses common natural variations or synonyms a user might say; no explicit trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

Naming a specific third-party tool ('Codemap CLI') gives it a clear niche with minimal conflict risk, though the generic 'codebase visualization and navigation' phrasing leaves minor overlap with other code-navigation skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

plugins/mcp/skills/setup-codemap-cli/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.