Content
86%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 an efficient, well-structured workflow with concrete commands and sensible edge-case guards. The main gaps are the unspecified frontmatter-editing mechanism and the lack of a check that the task file was uniquely located before the move.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — inputs, four numbered steps, and edge cases — with no explanation of concepts Claude already knows; every token earns its place. There is nothing to trim that would move it off the top anchor. | 5 / 5 |
Actionability | Concrete `find`, `mkdir -p`, and `mv` commands plus a real example invocation make the guidance mostly executable, but step 2 gives no concrete mechanism for editing the frontmatter and `<OLD_PRIORITY>` is never explicitly determined, keeping it below fully copy-paste-ready. | 4 / 5 |
Workflow Clarity | The find → update → move → report sequence is clear and the Important section supplies checkpoints (missing-args guard, already-at-priority guard, done/ guard). It falls short of a 5 because there is no validation that `find` located exactly one task file before moving it; the operation is a single-file move, so the destructive/batch cap at 3 does not apply. | 4 / 5 |
Progressive Disclosure | A single-purpose skill under 50 lines with well-organized sections (Inputs / Steps / Important) and no need for external reference files — per the rubric's simple-skill note, this earns the top score. | 5 / 5 |
Total | 18 / 20 Passed |