CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-goal

Manage condition goals or create and operate an approved autonomous mission

Quality

63%

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

Quality

Content

72%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 delegation wrapper that is perfectly token-efficient and needs no bundle structure, but it provides minimal executable detail beyond the bare invocation. Its weakest points are the unspecified argument surface and the absence of any validation step for what is inherently a risky autonomous-operation context.

Suggestions

Document the valid arguments the moai goal command accepts (e.g., one-line examples like `goal set <name>`, `goal status <id>`) so the delegation is executable rather than a placeholder pass-through.

Add a brief checkpoint before launching a mission, e.g. "Confirm the mission is approved before invoking; if moai is unavailable, report the failure instead of improvising."

DimensionReasoningScore

Conciseness

The body is a single delegation line — "Use Skill(\"moai\") with arguments: goal $ARGUMENTS" — with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching anchor 5 exactly.

5 / 5

Actionability

The instruction is concrete (a specific skill invocation with its argument prefix), but it is incomplete: "$ARGUMENTS" is an unsubstituted placeholder, the valid goal sub-arguments are unspecified, and there is no guidance for failure cases such as the moai skill being unavailable. This matches anchor 3 ('Some concrete guidance but incomplete... missing key details') rather than anchor 4's mostly-executable guidance.

3 / 5

Workflow Clarity

The single delegation step is unambiguous, but the skill's purpose — creating and operating an autonomous mission — is a batch/risky operation context with no validation checkpoint (e.g., confirming the mission is approved before launch). Per the rubric, workflows involving batch operations without validation are capped at 3.

3 / 5

Progressive Disclosure

This is a one-line skill with no bundle files (no references/, scripts/, or assets/ directories exist) and no content that belongs in separate files. The under-50-line simple-skill exception applies: there is nothing to disclose progressively and nothing is inlined or nested.

5 / 5

Total

16

/

20

Passed

Description

37%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 names a distinctive domain but relies on system jargon and generic verbs, giving users no natural trigger phrases and no guidance on when to invoke it. It reads as an auto-generated wrapper label rather than a capability description that supports correct skill selection.

Suggestions

Replace generic verbs with concrete actions, e.g. "Set, update, and track condition goals; launch, monitor, and report on approved autonomous moai missions."

Add an explicit trigger clause, e.g. "Use when the user wants to define a goal, start or supervise an autonomous mission, or check mission status."

Include natural user-facing synonyms and phrasings (goal, objective, mission, run autonomously, check progress) so the description matches what users actually say rather than moai-internal jargon.

DimensionReasoningScore

Specificity

The description names its domain ("condition goals", "approved autonomous mission") but the verbs are generic ("Manage", "create and operate") with no concrete actions describing what managing a goal or operating a mission actually entails, matching the anchor 'Names the domain but actions are minimal or generic'. It falls short of anchor 3 because no concrete, specific actions are listed.

2 / 5

Completeness

A 'what' is stated — "Manage condition goals or create and operate an approved autonomous mission" — but the 'when' is entirely absent with no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3. It sits above anchor 2 because two distinct capabilities are named rather than a purely vague 'what'.

3 / 5

Trigger Term Quality

"condition goals" and "approved autonomous mission" are system-specific jargon; only "goal" and "mission" function as semi-natural keywords, and the natural phrases a user would actually say are missing. This fits anchor 2 ('One or two generic keywords; missing the natural phrases users say') rather than anchor 1 because goal/mission are not pure technical jargon.

2 / 5

Distinctiveness Conflict Risk

The niche terms ("condition goals", "approved autonomous mission") give it some specificity, but the description substantially overlaps the parent moai skill it delegates to and could collide with generic goal/planning skills. This matches anchor 3 ('Somewhat specific but could still overlap with similar skills').

3 / 5

Total

10

/

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