Content
68%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 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |