CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-run

Implement SPEC requirements using DDD/TDD methodology

Quality

69%

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-run/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a maximally lean, unambiguous delegation stub that scores perfectly on conciseness and disclosure. Its weakness is actionability: it provides the invocation syntax but delegates all executable knowledge elsewhere, leaving no in-skill guidance on what the delegated command does or how to handle its results.

Suggestions

Add one line explaining what the delegated "run" command produces or what to do with its output, so the skill remains actionable even if the "moai" skill is unavailable.

State a fallback behavior for the $ARGUMENTS placeholder (e.g., what to pass or ask for when no arguments are supplied).

DimensionReasoningScore

Conciseness

The body is a single line — "Use Skill(\"moai\") with arguments: run $ARGUMENTS" — with zero padding and no explanation of concepts Claude already knows. It matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place").

5 / 5

Actionability

The instruction is concrete in form (exact skill name and exact argument format "run $ARGUMENTS"), but all substance is delegated to an external "moai" skill: nothing explains what the "run" argument does, there is no usage example, and "$ARGUMENTS" is an unresolved placeholder. This matches anchor 3 ("Some concrete guidance but incomplete... missing key details") rather than anchor 4's mostly-complete executable guidance.

3 / 5

Workflow Clarity

As a simple single-purpose skill the action is unambiguous — invoke skill "moai" with arguments "run <args>" — so the simple-skill exception applies. However, minor gaps remain: no guidance on handling the delegated skill's result, or what to do when $ARGUMENTS is empty, which places it at anchor 4 ("minor validation gaps") rather than a fully unambiguous 5.

4 / 5

Progressive Disclosure

The body is one line, well under 50 lines, with no bundle files (no references/, scripts/, or assets/ exist) and no need for external references. The entire content is a clearly signaled one-level-deep pointer, which per the simple-skills scoring note merits a 5.

5 / 5

Total

17

/

20

Passed

Description

45%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 states a terse "what" with a distinguishing methodology mention, but it lacks any "when to use" guidance, concrete actions beyond generic "implement", and natural trigger phrases. It is serviceable but reads more like an internal command summary than a skill description.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to implement a spec/SPEC file or requests DDD/TDD-style implementation with tests first."

Name concrete actions instead of a single generic verb, e.g., "Implements spec requirements as production code and tests using DDD/TDD: design domain models, write failing tests, implement, refactor."

Define or expand "SPEC" (e.g., the spec file format or location) so the description is self-explanatory rather than ambiguous jargon.

DimensionReasoningScore

Specificity

"Implement SPEC requirements using DDD/TDD methodology" names the domain but the only action is the generic "Implement"; DDD/TDD are methodology labels rather than concrete user-facing actions, matching anchor 2 ("Names the domain but actions are minimal or generic"). It falls short of anchor 3 because no concrete action beyond generic implementation is stated.

2 / 5

Completeness

A "what" is present ("Implement SPEC requirements using DDD/TDD methodology") but the "when" is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not 4 because anchor 4 requires both a "what" and an explicit "when".

3 / 5

Trigger Term Quality

Terms like "SPEC", "requirements", "DDD", and "TDD" are relevant keywords a user might plausibly say, but common variations, synonyms, and natural trigger phrases (e.g., "implement the spec", "write tests first") are missing. 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

"DDD/TDD methodology" gives the skill a niche, but "Implement SPEC requirements" overlaps broadly with general coding and implementation skills, and with no "when" guidance the trigger risk is moderate. This fits anchor 3 ("Somewhat specific but could still overlap with similar skills") better than anchor 4's minor-overlap-only bar.

3 / 5

Total

11

/

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