CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-review

Code review with security and @MX tag compliance check

Quality

77%

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

Quality

Content

92%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 minimal, clean delegation stub: one unambiguous executable instruction with no wasted tokens, no over-explanation, and no nested references. Its only weakness is that it handles just the base invocation, offering no argument examples or fallback guidance if the target skill is unavailable.

Suggestions

Add one line enumerating accepted arguments or common invocations (e.g., file paths, diff targets) to lift actionability from mostly-executable to fully copy-paste ready.

Note briefly what to do if the moai skill is unavailable or returns an error, so the single-step workflow has a recovery path.

DimensionReasoningScore

Conciseness

The entire body is one line — 'Use Skill("moai") with arguments: review $ARGUMENTS' — with zero padding and no explanation of concepts Claude already knows. This matches 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

The instruction is a concrete, executable command naming the exact skill ("moai") and argument pattern ("review $ARGUMENTS"), so it is not vague or pseudocode. It falls short of 5 because it covers only the base invocation — no guidance on valid arguments, targets, or common usage variations.

4 / 5

Workflow Clarity

This is a single-purpose skill under 50 lines with one unambiguous action — invoke Skill("moai") with 'review' plus the user's arguments — so the simple-skill exception applies and workflow clarity can score 5. The operation is not destructive or batch-oriented, so no validation cap applies.

5 / 5

Progressive Disclosure

The body is one line with no bundle files (no references/, scripts/, or assets/ exist), and its only pointer is a single clearly-signaled, one-level-deep delegation to the moai skill. There is nothing that should be split out, and navigation is trivial — matching the under-50-lines/no-external-references case the rubric scores at 5.

5 / 5

Total

19

/

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 states a clear 'what' with a recognizable niche (@MX tag compliance), but it lacks any 'when to use' guidance, offers thin action detail, and leans on generic trigger terms that risk overlap with other review skills. It sits at the midpoint of the rubric across all dimensions.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks to review code, a diff, or a PR, or mentions @MX tags or security compliance.'

Include natural synonyms users would say — "review my code", "PR review", "security audit", "compliance check" — to improve trigger-term coverage.

Briefly enumerate what the review covers (e.g., bugs, vulnerabilities, tag violations) so the 'what' goes beyond naming the domain.

DimensionReasoningScore

Specificity

The description names the domain ("Code review") and two concrete checks ("security" and "@MX tag compliance check"), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It does not reach 4 because it never elaborates what the review covers or how the checks operate, leaving coverage thin.

3 / 5

Completeness

The 'what' is stated clearly (code review with security and @MX tag compliance checking) but there is no 'when' clause whatsoever — no "Use when..." or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant natural terms are present ("Code review", "security", "compliance"), but common variations users would actually say are missing — e.g., "review my code", "PR review", "security audit", "vulnerability scan". This matches 'Some relevant keywords but missing common variations or synonyms'; it is not 4 because several high-frequency natural phrases are absent.

3 / 5

Distinctiveness Conflict Risk

The "@MX tag compliance" fragment carves out a niche, but the leading "Code review with security" phrase is broad and would overlap with generic code-review and security-review skills. This fits 'Somewhat specific but could still overlap with similar skills'; not 4 because the dominant trigger term is generic enough to collide with common review skills.

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

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