CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-codemap-cli

Guide for setup Codemap CLI for intelligent codebase visualization and navigation

40

Quality

40%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

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

57%

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

The skill is highly actionable with concrete, executable commands and well-structured step-by-step guidance for setting up Codemap CLI. Its main weaknesses are the monolithic structure—embedding large JSON configs and markdown templates inline rather than referencing separate files—and the lack of explicit error handling or validation feedback loops for potentially fragile operations like merging settings files or handling installation failures.

Suggestions

Extract the full hooks JSON example and the CLAUDE.md template content into separate bundle files (e.g., HOOKS_FULL_CONFIG.json, CLAUDE_TEMPLATE.md) and reference them from the main skill to improve progressive disclosure and reduce token usage.

Add validation/error recovery guidance for key steps: what to do if installation fails, how to handle merging hooks into an existing settings.json that already has content, and how to verify the settings file is valid JSON after editing.

Remove or condense the options table in the CLAUDE.md block—Claude can reference the README directly, and duplicating CLI documentation increases maintenance burden and token cost.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary verbosity—the full hooks JSON example is quite long and could be referenced externally, and the CLAUDE.md content block is extensive. However, it mostly avoids explaining concepts Claude already knows and stays focused on actionable setup steps.

2 / 3

Actionability

The skill provides fully executable commands for installation (brew, scoop), verification, and configuration. JSON configs are copy-paste ready, CLI flags are documented with concrete examples, and conditional logic (e.g., non-main default branch) is clearly specified.

3 / 3

Workflow Clarity

Steps are clearly numbered and sequenced (1-9), and there's a verification step after installation. However, there are no explicit validation checkpoints or error recovery loops—e.g., what to do if `codemap -help` fails for reasons other than not being installed, or if `brew install` fails. The settings file creation step lacks validation that the JSON is correctly merged with existing settings.

2 / 3

Progressive Disclosure

The skill is a monolithic wall of content with no references to external files. The full hooks JSON example (~40 lines), the complete CLAUDE.md content block, and the options table are all inline. These could be split into separate reference files (e.g., HOOKS_REFERENCE.md, CLAUDE_TEMPLATE.md) with the SKILL.md serving as an overview.

1 / 3

Total

8

/

12

Passed

Description

22%

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 is too vague and lacks concrete actions, explicit trigger guidance, and natural user keywords. It reads more like a title than a functional description that would help Claude distinguish this skill from others. The mention of 'Codemap CLI' provides some specificity but the overall description fails to communicate what the skill actually does or when it should be used.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about setting up Codemap, visualizing code dependencies, or navigating project structure.'

List specific concrete actions the skill covers, e.g., 'Guides installation and configuration of Codemap CLI, generates dependency graphs, creates interactive code maps, and sets up project-level navigation.'

Include natural trigger terms users would say, such as 'install codemap', 'code structure', 'dependency visualization', 'project map', 'codebase overview'.

DimensionReasoningScore

Specificity

The description says 'setup Codemap CLI for intelligent codebase visualization and navigation' which names a tool and vague capabilities ('visualization and navigation') but doesn't list concrete actions like generating dependency graphs, creating file maps, or navigating call hierarchies.

1 / 3

Completeness

The description only vaguely addresses 'what' (setup guide for Codemap CLI) and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 2, and the weak 'what' brings it to 1.

1 / 3

Trigger Term Quality

Contains some relevant keywords like 'Codemap CLI', 'codebase visualization', and 'navigation' that users might mention, but misses common variations and natural terms users would say such as 'code map', 'dependency graph', 'project structure', or 'install codemap'.

2 / 3

Distinctiveness Conflict Risk

Mentioning 'Codemap CLI' specifically provides some distinctiveness as a named tool, but 'codebase visualization and navigation' is broad enough to overlap with other code analysis or documentation skills.

2 / 3

Total

6

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
NeoLabHQ/context-engineering-kit
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.