Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is concise, actionable, and well-organized for a simple single-purpose skill, with copy-paste-ready commands and clear sequencing. The main gap is the absence of a validation/verification checkpoint for the destructive file-move step.
Suggestions
Add a validation checkpoint before the move: confirm `find` returned exactly one file and abort with a clear message if zero or multiple matches are found.
Verify the `mv` succeeded (e.g. check the file exists in the destination) and confirm the frontmatter `priority` field actually changed, retrying or reporting on failure.
For Step 2, consider giving an executable frontmatter-edit command (e.g. a `yq`/`sed` snippet) rather than only the target yaml line, to keep every step copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — tight Inputs, four numbered steps with compact code/report blocks, a short guardrail list, and "$ARGUMENTS" — with no explanation of concepts Claude already knows. It matches the anchor for lean, efficient content where every token earns its place, and is above anchor 2 because there is nothing unnecessary to trim. | 3 / 3 |
Actionability | Executable commands are provided copy-paste-ready with placeholders: `find ... -name "<TASK_ID>.md" -not -path "*/done/*"`, `mkdir -p ...`, and `mv ...`, plus a concrete frontmatter edit. It matches the anchor for fully executable commands with specific examples; it is above anchor 2 because these are real bash commands, not pseudocode. | 3 / 3 |
Workflow Clarity | The four steps (find → update frontmatter → move → report) are clearly sequenced with guardrails ("Never move tasks from done/", "If already at the requested priority, do nothing"), but there is no validation checkpoint for the destructive `mv` operation. Per the rubric, missing validation for destructive operations caps workflow clarity at 2; it is above anchor 1 because the sequence is clear and well-ordered. | 2 / 3 |
Progressive Disclosure | This is a self-contained skill under ~50 lines with well-organized sections (Inputs, Steps, Important) and no external references needed; no bundle files exist. Per the guideline, such simple skills can score 3 with just well-organized sections, and it is above anchor 2 because the content is organized, not a monolithic wall. | 3 / 3 |
Total | 11 / 12 Passed |