CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codemap

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/codemap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-structured, largely executable workflow skill with verified commands and good organization. Its weaknesses are the missing verification loop after fixer agents batch-write codemaps (capping workflow clarity) and unspecified mechanics for spawning fixers.

Suggestions

Add a validation checkpoint after fixer agents run: verify each codemap.md is non-empty and well-formed (e.g., re-run codemap.mjs changes or spot-check files) before running codemap.mjs update, with a retry loop for failed folders.

Make fixer delegation concrete: show the exact command or prompt template used to spawn a fixer (target folder, file to write, and the content spec to follow) instead of just "Spawn one fixer per folder".

Consider moving the Codemap Content section (responsibility/design/flow/integration spec and skeleton) into a references/ file, keeping only a one-line pointer in the main workflow.

DimensionReasoningScore

Conciseness

The body is dense workflow instruction with no padding of concepts Claude already knows; only minor spots could be trimmed (e.g., "This file serves as the Master Entry Point for any agent or human entering the repository").

4 / 5

Actionability

Commands are concrete, executable, and verified against scripts/codemap.mjs (init/changes/update with --root/--include/--exclude), plus explicit globs, a skeleton, and an AGENTS.md template; "Spawn one fixer per folder" lacks the concrete spawn mechanics, a minor gap.

4 / 5

Workflow Clarity

The 5-step sequence is clear with conditionals, legacy migration, and idempotent AGENTS.md handling (a 4-level structure), but the workflow batch-writes codemaps across all folders and delegates to fixers with no verification step before running update, so the batch-operation validation cap applies.

3 / 5

Progressive Disclosure

Scored against the actual bundle (scripts/codemap.mjs present, no references/ or assets/): the script reference is clear including the base-directory resolution note, sections are well-organized, and inline material is short enough to stay inline; the codemap content spec could still live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

78%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.

A strong description that explicitly answers both what and when, with a useful cost warning to prevent over-triggering. Its main gap is specificity: it names a single action rather than enumerating the concrete outputs (state init, per-folder codemaps, root atlas, AGENTS.md registration).

DimensionReasoningScore

Specificity

"Generate comprehensive hierarchical codemaps" names the domain with one concrete action; the rest of the description is usage guidance rather than additional capabilities, matching the anchor for 1-2 concrete actions rather than several.

3 / 5

Completeness

It clearly states what ("Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories") and an explicit when with concrete trigger phrases ("only use when explicitly asked for codebase documentation or initial repository mapping"), matching the top anchor on both counts.

5 / 5

Trigger Term Quality

"codemaps", "codebase documentation", and "repository mapping" are natural user phrases, but common variations like "understand the codebase" or "architecture overview" are missing, fitting the good-but-not-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"Codemaps" is a distinct niche, but "codebase documentation" overlaps with documentation-generation and init-style skills, fitting the mostly-distinct anchor with minor overlap risk.

4 / 5

Total

16

/

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

relative_links

Relative link issues: 1 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

alvinunreal/oh-my-opencode-slim

Path

src/skills/codemap/SKILL.md

Revision

4076743

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill