Content
78%Weight 40%Scale 1-5Reviews 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 one-line delegation stub: perfectly token-efficient and structurally clean, with an unambiguous single step and a clearly signaled one-level reference. However, it delegates 100% of the skill's substance to an external "moai" skill without defining $ARGUMENTS, describing the expected output, or providing any fallback, leaving actionability incomplete.
Suggestions
Define what $ARGUMENTS should contain (e.g. the feature or task to plan) and show one example invocation, such as Skill("moai") with arguments: plan "add user login flow".
Add a sentence stating the expected deliverable (the SPEC document with EARS requirements) and a fallback if the moai skill is unavailable — e.g. draft the SPEC directly using EARS syntax ("When [trigger], the system shall [response]").
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a single line — "Use Skill("moai") with arguments: plan $ARGUMENTS" — with zero padding and every token load-bearing; it fully assumes the executor's competence. Matches anchor 5; not 4 because there is nothing to trim. | 5 / 5 |
Actionability | The one directive is concrete (exact tool name "moai" and argument string "plan $ARGUMENTS"), but key details are missing: $ARGUMENTS is never defined, there is no guidance on what the delegated call produces, no fallback if the moai skill is unavailable, and nothing about the stated deliverable (SPEC with EARS requirements) is covered here. Matches anchor 3 (concrete but incomplete); not 4 because the gaps are not minor — the entire substance of the task lives in another skill. | 3 / 5 |
Workflow Clarity | The single step is unambiguous and precisely specified (invoke Skill "moai" with "plan $ARGUMENTS"), and no destructive or batch operations are involved, but there is no articulation of what follows delegation or how to confirm the SPEC was actually produced. Not 5 because the undefined placeholder and absent outcome check leave a minor gap; not 3 because the one required action cannot be misunderstood. | 4 / 5 |
Progressive Disclosure | The body is one line with nothing that belongs in a separate file, and no bundle files (references/, scripts/, assets/) exist to organize; its single reference — delegation to the "moai" skill — is explicit and one level deep. Matches the simple-skill exception for reference-free, well-organized content; not 4 because there is no content misplacement or buried reference. | 5 / 5 |
Total | 17 / 20 Passed |