CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

task-prioritize

Reprioritize a devflow task — move between priority folders (P0-P4) and update frontmatter.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/task-prioritize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews 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.

DimensionReasoningScore

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

Description

53%Weight 40%Scale 1-5

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, specific to its niche, and states two concrete actions, but it lacks any "Use when..." trigger guidance and misses natural trigger synonyms, which limits discoverability and completeness. Adding an explicit trigger clause would raise both completeness and trigger-term quality.

Suggestions

Add a "Use when..." clause, e.g., "Use when the user asks to change, reprioritize, or move a devflow task between priority levels."

Include natural trigger synonyms such as "change priority", "move task", "promote/demote" alongside "reprioritize".

Briefly mention the P0-P4 scale meaning or the done-folder guard so the scope is comprehensive, not just two actions.

DimensionReasoningScore

Specificity

"move between priority folders (P0-P4)" and "update frontmatter" name the devflow-task domain plus exactly two concrete actions, matching the score-3 anchor; it is not 4 because coverage of the reprioritization workflow is not comprehensive (no mention of reporting or the done-folder rule).

3 / 5

Completeness

The "what" is clear (move between priority folders, update frontmatter), but there is no "Use when..." clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3.

3 / 5

Trigger Term Quality

"Reprioritize", "priority", "task", and "P0-P4" are relevant keywords, but common natural variations users would say ("change priority", "move task", "promote/demote a task") are missing, matching the score-3 anchor rather than 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"devflow task" plus "reprioritize" carves a mostly distinct niche with only minor overlap risk against closely related devflow task-management skills (e.g., a task-edit or task-move skill); it is not 5 because no explicit triggers further reduce conflict risk.

4 / 5

Total

13

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AndreJorgeLopes/devflow

Path

skills/task-prioritize/SKILL.md

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.