Content
100%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.
An exemplary lean skill body: every token is operational guidance Claude would not infer on its own, the single workflow is unambiguous with validation checkpoints and safe defaults, and structure is appropriate for a self-contained skill. No weaknesses identified.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~27-line body is lean and assumes Claude's competence, with every sentence adding non-obvious operational constraints ("Pass the prompt as one quoted argument", "never pass `--permission full`", "Never start the interactive TUI"). There is no padding or explanation of known concepts, matching the top anchor. | 5 / 5 |
Actionability | Provides a copy-paste-ready command (`mcode exec "<prompt>"`), a concrete availability check (`command -v mcode`), specific permission flags with an explicit prohibition, and a worked example (explain a failing test without editing). The specific examples cover the common cases, matching the fully-executable anchor. | 5 / 5 |
Workflow Clarity | A clear sequence (set cwd and timeout, availability check with stop-and-ask, run one task, treat nonzero exit as failure) with explicit validation checkpoints and error-recovery guidance for missing auth/config. The destructive-operation cap does not apply because modifications are gated on explicit user request with a read-only default, and this simple single-purpose skill has an unambiguous action. | 5 / 5 |
Progressive Disclosure | The skill is under 50 lines, needs no external references (no references/scripts/assets bundle exists), and is organized into two clear sections ("Run", "Authentication And Permissions"). Per the rubric's guidance for simple skills, well-organized sections alone merit the top score. | 5 / 5 |
Total | 20 / 20 Passed |