Content
87%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 instruction-only skill: lean, fully concrete, with copy-paste commands, exact schemas, and a clear resume sequence. Its one real gap is the missing verification loop around the destructive `mc mirror --overwrite` push, which the skill's own gotcha about losing unpushed work makes conspicuous.
Suggestions
Add a validation step after the `mc mirror` push (e.g. re-list the remote directory or check the command's exit output) and instruct to retry on failure, since the skill's own gotcha warns that session resets can lose unpushed work.
Clarify what to do if `task-history.json` has no entry for the task-id (e.g. fall back to listing the shared tasks directory) so the resume flow handles the missing-history edge case.
Specify the timezone convention for `HH:MM` and `YYYY-MM-DD` timestamps so progress entries sort deterministically across machines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries non-obvious, environment-specific information (exact paths, the LRU-10 rule, the mc mirror command, the log entry template); there is no explanation of concepts Claude already knows and no padding. This matches the lean anchor — nothing could be trimmed without losing information. | 5 / 5 |
Actionability | Fully executable throughout: exact file paths, a copy-paste `mc mirror ... --overwrite --exclude "spec.md"` command, a complete JSON example for task-history.json, an exact markdown template for log entries, and a concrete numbered resume procedure. Nothing is pseudocode or hand-wavy. | 5 / 5 |
Workflow Clarity | The resume flow is a clear numbered sequence and the LRU/status rules are explicit, but the `mc mirror --overwrite` push is a destructive batch operation with no validation checkpoint that the push succeeded — even though the gotcha itself warns "session resets can lose unpushed work". Per the rubric guideline, a workflow with a destructive/batch step and no verification caps at 3; it is not 2 because the sequences themselves are complete and unambiguous. | 3 / 5 |
Progressive Disclosure | This is a compact single-file skill (~65 lines) with no bundle files present (no references/, scripts/, or assets/ directories exist) and no external references needed; the content is appropriately inlined and well-organized under clear Gotchas / Progress Log / Task History / Resume Flow headers. Per the rubric's simple-skill guidance, well-organized sections with no need for external references score 5. | 5 / 5 |
Total | 18 / 20 Passed |