task-prioritize
Reprioritize a devflow task — move between priority folders (P0-P4) and update frontmatter.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/task-prioritize/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is concise and specific about what it does — reprioritizing devflow tasks by moving them between P0-P4 folders and updating frontmatter. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The domain-specific terminology makes it distinctive but could benefit from more natural trigger terms.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to change, bump, or reassign the priority of a devflow task.'
Include natural trigger term variations such as 'change priority', 'bump priority', 'reassign priority', 'move task priority' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: 'move between priority folders (P0-P4)' and 'update frontmatter'. These are specific, actionable operations rather than vague language. | 3 / 3 |
Completeness | Clearly answers 'what' (move between priority folders and update frontmatter) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'reprioritize', 'priority folders', 'P0-P4', and 'frontmatter', but misses natural user phrases like 'change priority', 'bump priority', 'move task', or 'devflow' task management variations. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific combination of 'devflow task', 'priority folders (P0-P4)', and 'frontmatter' — this is a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise skill that provides clear executable commands and a logical workflow for reprioritizing tasks. Its main weakness is the lack of validation steps — particularly verifying the task file exists before attempting to update and move it, which could lead to errors on missing files. The constraints section appropriately guards against moving completed tasks.
Suggestions
Add a validation step after the find command to check that exactly one file was found before proceeding (e.g., handle cases where the task ID doesn't match any file or matches multiple files).
Add a verification step after the move to confirm the file exists at the new location.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose — inputs, steps, constraints. No unnecessary explanations of what priorities are or how file systems work. The hardcoded paths are necessary context Claude wouldn't know. | 3 / 3 |
Actionability | Provides fully executable bash commands for finding and moving files, clear YAML syntax for the frontmatter update, and a concrete output template. The example invocation makes usage unambiguous. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and the workflow is logical. However, there's no validation checkpoint — e.g., verifying the task file was actually found before proceeding, or confirming the frontmatter was correctly updated before moving. For a file-moving operation, a check that the find command returned a result is important. | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized into clear sections (Inputs, Steps, Important) making it easy to follow. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- AndreJorgeLopes/devflow
- Commit
b0b1bb6
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.