codemap

Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/skills/codemap/SKILL.md

Quality

Content

65%

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 real, executable commands and a clear multi-step workflow, but it is held back by verbose inline example templates and a missing validation checkpoint for its batch fixer-delegation step.

Suggestions

Add an explicit validation step after fixers write codemaps (e.g., verify each codemap.md has the required Responsibility/Design/Flow/Integration sections before running update) to close the feedback loop.

Move the two long example codemap templates into a references/ file (e.g., references/codemap-template.md) and link to it, keeping SKILL.md a lean overview.

Trim or remove the "When to Use" section since it duplicates the frontmatter description.

Dimension	Reasoning	Score
Conciseness	It avoids explaining basics Claude already knows and uses concrete commands, but the two full inline example codemap templates and the redundant "When to Use" section could be tightened.	2 / 3
Actionability	It provides concrete, copy-paste-ready bash commands invoking the real scripts/codemap.mjs (init/changes/update) plus explicit include/exclude glob patterns and filled-out codemap templates.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced with branching state checks, but this batch operation (one fixer per folder) lacks an explicit validation/verification checkpoint confirming codemap accuracy before finalizing, which caps the score at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned and references the real bundle script scripts/codemap.mjs one level deep, but the bulk of guidance and both large example templates live inline in SKILL.md rather than in separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 cleanly answers both what it does and when to use it, with a distinctive, well-scoped niche. Its main weakness is trigger-term naturalness and a single-action specificity rather than multiple concrete capabilities.

Suggestions

Add a few natural user phrasings as triggers (e.g., "use when the user asks to understand, explore, or document an unfamiliar codebase").

List additional concrete actions (e.g., "detect changed files and incrementally update existing codemaps") to lift specificity toward 3.

Dimension	Reasoning	Score
Specificity	"Generate comprehensive hierarchical codemaps" names one concrete action and the domain ("UNFAMILIAR repositories"), but it does not enumerate multiple distinct actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It states what ("Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories") and an explicit when ("only use when explicitly asked for codebase documentation or initial repository mapping"), clearly answering both.	3 / 3
Trigger Term Quality	"codebase documentation" and "initial repository mapping" are relevant, but "codemaps" and "repository mapping" are technical phrasings and it misses common natural variants like "understand this codebase" or "explore the repo".	2 / 3
Distinctiveness Conflict Risk	The niche (codemap generation for unfamiliar repos) is narrow and the "Expensive operation - only use when explicitly asked" scoping further reduces the chance of triggering for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 3 missing, 3 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: alvinunreal/oh-my-opencode-slim
Path: src/skills/codemap/SKILL.md
Commit: 1c0e1f4

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.