CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup-codemap-cli

Guide for setup Codemap CLI for intelligent codebase visualization and navigation

Quality

71%

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 ./antigravity/skills/setup-codemap-cli/SKILL.md

The canonical home for this skill is setup-codemap-cli in NeoLabHQ/context-engineering-kit

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-sequenced, highly actionable setup guide built almost entirely from executable commands and copy-paste templates, with verification steps at the right points. Its main defects are a contradictory and invalid minimal hooks snippet in step 9, redundant verification steps, and the absence of any error-recovery guidance.

Suggestions

Remove or fix the invalid minimal hooks snippet in step 9 ("hooks": {"session-start": "..."}) so it matches the correct matcher-array format shown in the full example; contradictory formats risk Claude writing a non-functional settings file.

Merge the overlapping verification in steps 5 and 8 (both run `codemap .`/`codemap --diff`) into a single validate step, and add brief error-recovery guidance for when installation or verification fails.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands and copy-paste templates with no explanations of concepts Claude already knows. Minor tightening is possible: steps 5 and 8 both run `codemap .`/`codemap --diff` redundantly, and step 9's minimal hook snippet duplicates (and contradicts) the full hooks example below it.

4 / 5

Actionability

Nearly all guidance is copy-paste ready (brew/scoop commands, CLAUDE.md template, full hooks JSON), but step 9's first snippet uses a flat string map ("hooks": {"session-start": "..."}) that is not a valid hooks settings format and conflicts with the correct array-of-matchers structure shown later, which is a real gap.

4 / 5

Workflow Clarity

A clear numbered sequence (steps 1-9) with an explicit context decision in step 1 and verification checkpoints in steps 2, 5, and 8. It falls short of 5 because there is no error-recovery guidance (e.g., what to do if `brew install` fails or `codemap .` errors after install).

4 / 5

Progressive Disclosure

Good section structure with clearly signaled content, no nested references, and one clearly signaled external reference (the Codemap README URL). The large inline templates (CLAUDE.md block, full hooks JSON) are defensible for verbatim copy-paste during setup, though the ~67-line hooks example could live in a separate reference file.

4 / 5

Total

16

/

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 identifies a specific tool and purpose but is held back by awkward phrasing ("Guide for setup"), a buzzword ("intelligent"), and the complete absence of any "when to use" trigger guidance. It is serviceable but below the quality of the reference good examples, which pair concrete actions with explicit trigger clauses.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to set up, install, or configure Codemap CLI, or wants codebase visualization/navigation tooling."

List the concrete actions the skill performs (install via Homebrew/Scoop, verify installation, update CLAUDE.md, configure hooks in settings.json) instead of the single generic action "setup".

Fix the grammar ("Guide for setup" -> "Guide to setting up") and drop the buzzword "intelligent"; include natural trigger variations like "code map", "explore codebase", "visualize project structure".

DimensionReasoningScore

Specificity

The description names the domain ("setup Codemap CLI") and 1-2 capability areas ("codebase visualization and navigation"), but "intelligent" is buzzword and the only concrete action is the setup itself. It is above the generic anchor (2) because a specific tool and purpose are named, but not comprehensive enough for 4.

3 / 5

Completeness

It has a clear "what" (guide for setting up Codemap CLI for visualization/navigation) but no "when" or "Use when..." trigger guidance at all; per the judging guidelines a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant keywords ("Codemap CLI", "codebase", "visualization", "navigation", "setup") but misses natural variations and synonyms users would say, such as "set up codemap", "explore codebase", or "code map". Matches the "some relevant keywords but missing common variations" anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific tool "Codemap CLI" gives it a distinct niche with minimal conflict risk, though "codebase visualization and navigation" slightly overlaps with generic code-navigation skills. Mostly distinct with minor overlap, matching anchor 4 rather than 5.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NeoLabHQ/context-engineering-kit

Path

antigravity/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.