Content
72%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 skill body is concise, actionable, and well-structured for a simple single-purpose task, but its destructive file-move and frontmatter-rewrite workflow lacks any validation checkpoints, capping workflow clarity. Adding a verify step would meaningfully raise the score.
Suggestions
Add a validation checkpoint after the find step: confirm the task file exists and is not under done/ before proceeding, and abort with a clear message if missing.
Add a post-move verification (e.g. confirm the file now resides under the new priority folder and frontmatter priority matches) to close the destructive-operation feedback loop.
Replace hardcoded absolute paths (/Users/andrejorgelopes/dev/devflow/tasks) with a parameter or resolved base path so the commands are portable and executable across environments.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; only minor trimmable elements (the trailing $ARGUMENTS line and a couple of redundant guard notes) keep it just below a 5. | 4 / 5 |
Actionability | It provides concrete, copy-paste-ready commands (find, mkdir -p, mv) and a frontmatter snippet with placeholders, but hardcoded absolute paths and unfilled placeholders leave minor execution gaps. | 4 / 5 |
Workflow Clarity | The four steps are clearly sequenced, but this destructive operation (moving a file and rewriting frontmatter) has no validation checkpoint (verify file exists, confirm not in done/, verify after move), which caps workflow clarity at 3 per the rubric. | 3 / 5 |
Progressive Disclosure | This under-50-line single-purpose skill has no need for external references and is well-organized into Inputs, Steps, and Important sections, qualifying for the simple-skill exception at 5. | 5 / 5 |
Total | 16 / 20 Passed |