CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-project

Generate project documentation (product.md, structure.md, tech.md, codemaps/)

Quality

71%

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 ./.agents/skills/moai-project/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.

The body is maximally lean (a single unambiguous delegation line) but provides almost no actionable substance: the argument placeholder is undocumented and the target skill is outside the bundle. It functions as a publisher stub rather than a self-contained instruction, which caps actionability and workflow safety.

Suggestions

Show one concrete example invocation with real arguments, e.g. Skill("moai") with arguments: project src/ --output docs/, to make the delegation copy-paste ready and remove the opaque $ARGUMENTS placeholder.

Add a brief note on what happens on execution (which files are created/overwritten) and a validation step before overwriting existing documentation, since batch file generation is destructive to prior edits.

Document what the 'moai' skill expects (a one-line summary or a pointer to where its full instructions live) so the body does not rely on an external target that is not part of this bundle.

DimensionReasoningScore

Conciseness

The entire body is a single line — "Use Skill(\"moai\") with arguments: project $ARGUMENTS" — with no padding and no explanation of concepts Claude already knows, matching the 'lean and efficient, every token earns its place' anchor. There is nothing that could be trimmed, so it cannot be a 4.

5 / 5

Actionability

The line gives an exact invocation syntax (concrete guidance) but "$ARGUMENTS" is an undocumented placeholder and nothing explains what the target skill does or what valid arguments look like, matching anchor 3 for incomplete concrete guidance. It is above a 2 because the precise invocation is more concrete than a high-level hint, but below a 4 because it is not copy-paste ready for a real request.

3 / 5

Workflow Clarity

The single written action (invoke Skill("moai") with `project` args) is unambiguous, but the task it launches is a batch write operation (generating/overwriting multiple documentation files) with no validation or verification steps, so the destructive/batch cap holds workflow clarity at 3. It is not a 2 because the one step that is written is precisely defined, not poorly specified.

3 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ are absent), the body is minimal with nothing inlined that belongs elsewhere, and the delegation to Skill("moai") is a clearly signaled one-level reference — matching anchor 4. It is not a 5 because the body has no sections or organization at all and the referenced target skill is external to this bundle, leaving navigation opaque.

4 / 5

Total

15

/

20

Passed

Description

58%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 is concrete and specific about outputs (four named files) but omits any trigger guidance for when the skill should be used, capping its completeness and natural-term coverage. Overall a decent description that would score much higher with an explicit 'Use when...' clause.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. "Use when the user asks to generate or update project docs, describe the codebase, or produce architecture/tech documentation" — this lifts the completeness cap.

Include natural synonyms users would actually say, such as "docs", "codebase overview", "project structure", and "architecture", to improve trigger-term coverage.

Briefly say what each output file contains (e.g. "product.md for product overview, tech.md for tech stack") to raise specificity from good to comprehensive.

DimensionReasoningScore

Specificity

"Generate project documentation (product.md, structure.md, tech.md, codemaps/)" enumerates four concrete output artifacts in third person, matching the anchor for several specific actions with minor gaps. It is not a 5 because only the 'generate' action is covered with no detail on what each file contains, and not a 3 because the concrete filename list exceeds the 1-2-action level of specificity.

4 / 5

Completeness

The description gives a clear 'what' (generate named documentation files) but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It cannot be a 4 because that anchor requires both a 'what' and a 'when' to be present.

3 / 5

Trigger Term Quality

Keywords like "project documentation", "tech.md", and "codemaps/" are relevant, but common natural variations users would say ("docs", "codebase overview", "architecture", "document the project") are missing, matching the 'some relevant keywords but missing variations' anchor. It is above a 2 because the terms are far more specific than generic language like "works with files".

3 / 5

Distinctiveness Conflict Risk

The specific filenames (product.md, structure.md, tech.md, codemaps/) carve out a mostly distinct niche with only minor overlap risk against generic README or docs-generator skills, matching anchor 4. It is not a 5 because the claimed domain "project documentation" is broad and could collide with other documentation skills.

4 / 5

Total

14

/

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

.agents/skills/moai-project/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.