CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-codemaps

Scan codebase and generate architecture documentation in codemaps/

Quality

74%

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 ./internal/template/templates/.agents/skills/moai-codemaps/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 an exceptionally lean, well-targeted dispatcher that gives concrete invocation instructions for both harness types with no wasted tokens. Its only weakness is the fallback path deferring to external routing without local specifics or a failure checkpoint.

DimensionReasoningScore

Conciseness

The body is four lean lines with zero padding and no explanations of concepts Claude already knows; every line is an instruction ('Dispatch the moai workflow codemaps', 'invoke Skill("moai") with arguments: codemaps $ARGUMENTS'). This matches anchor 5 — 'lean and efficient; assumes Claude's competence; every token earns its place' — and is clearly not anchor 4 since there is nothing to trim.

5 / 5

Actionability

The primary path is concrete and executable ('invoke Skill("moai") with arguments: codemaps $ARGUMENTS'), and the fallback names a specific file path to read. It falls short of anchor 5 because the fallback instruction 'follow its routing for the codemaps subcommand' defers the actual steps to an external file rather than giving copy-paste-ready guidance, leaving minor gaps.

4 / 5

Workflow Clarity

As a simple single-purpose dispatcher, the action is unambiguous and the two harness cases are clearly delineated, which would justify a 5 under the simple-skill exception. However, the fallback branch's sequence is left implicit ('follow its routing') and there is no checkpoint for what to do if the moai skill or mirrored file is missing — minor validation gaps that place it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and nothing that belongs in separate files is inlined. The single external reference (~/.agents/skills/moai/SKILL.md) is one level deep and clearly signaled per harness case, matching both the simple-skill guideline and anchor 5's 'clear overview with well-signaled one-level-deep references'.

5 / 5

Total

18

/

20

Passed

Description

50%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 communicates a clear, concrete purpose but is minimal: it answers 'what' without any 'when to use' guidance and lacks natural trigger synonyms. It reads as an auto-generated one-liner rather than a description optimized for skill triggering.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user asks to map the codebase, document architecture, or generate code maps') to raise completeness.

Include natural synonyms and variations users would say — 'code map', 'architecture diagram', 'understand the codebase' — to improve trigger term coverage.

Briefly state what the generated documentation includes (e.g., components, dependencies, data flow) to sharpen specificity and distinctiveness against generic documentation skills.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — 'Scan codebase' and 'generate architecture documentation in codemaps/' — including the output location, but coverage is not comprehensive (no mention of what the documentation contains or formats produced). It is more concrete than anchor 2 ('minimal or generic actions') but does not list several specific actions required for anchor 4.

3 / 5

Completeness

The 'what' is clearly stated (scan codebase, generate architecture documentation in codemaps/), but there is no 'Use when...' clause or any equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not anchor 2 because the 'what' is concrete, not vague; not anchor 4 because 'when' is entirely absent rather than just implicit.

3 / 5

Trigger Term Quality

'codebase', 'architecture documentation', and 'codemaps' are relevant keywords a user might plausibly say, but common variations and synonyms are missing (e.g., 'code map', 'architecture diagram', 'understand the codebase'). This matches anchor 3 ('some relevant keywords but missing common variations or synonyms') rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'codemaps/' gives it a distinct output niche, but 'scan codebase and generate documentation' is broadly phrased and could overlap with general documentation-generation or code-analysis skills. This sits at anchor 3 ('somewhat specific but could still overlap with similar skills'), below anchor 4's 'mostly distinct; minor overlap risk'.

3 / 5

Total

12

/

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

modu-ai/moai-adk

Path

internal/template/templates/.agents/skills/moai-codemaps/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.