Content
65%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 content is a lean, well-organized, single-purpose procedure with concrete commands, but it has actionable gaps: a user-specific hardcoded tasks path, no step to determine the old priority folder or to perform the frontmatter edit, and no validation checkpoints around the find and mv operations. Fixing the path parameterization and adding verification steps would lift actionability and workflow clarity.
Suggestions
Replace the hardcoded "/Users/andrejorgelopes/dev/devflow/tasks" path with a parameter (e.g., a $TASKS_DIR variable or a documented config lookup) and define it once.
Add a step to read the task's current frontmatter to determine <OLD_PRIORITY> before the move, and give an executable command for the frontmatter edit.
Add validation checkpoints: check the find output is exactly one file, and verify the mv succeeded before reporting the change.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no over-explanation of concepts Claude already knows, but the hardcoded absolute path "/Users/andrejorgelopes/dev/devflow/tasks" is repeated four times instead of being defined once, a minor inefficiency keeping it below the score-5 anchor. | 4 / 5 |
Actionability | Concrete find/mkdir/mv commands are provided, but step 2 ("Update frontmatter") gives no executable command, the <OLD_PRIORITY> placeholder is never determined by any step, and the user-specific hardcoded path makes the commands non-executable on any other machine — missing key details per the score-3 anchor, worse than 4's "minor gaps". | 3 / 5 |
Workflow Clarity | The find → edit → move → report sequence is clearly ordered, but there is no validation of the find output (missing file or multiple matches), no verification that the move succeeded, and moving task files is a destructive filesystem operation — the judging guideline caps such workflows at 3. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines, single-purpose, needs no external reference files, and is cleanly organized into Inputs, Steps, and Important sections, satisfying the simple-skill exception for a top score. | 5 / 5 |
Total | 15 / 20 Passed |