CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

task-prioritize

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

Quality

76%

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 ./devflow-plugin/skills/task-prioritize/SKILL.md

The canonical home for this skill is task-prioritize in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is an efficient, well-structured workflow with concrete commands and sensible edge-case guards. The main gaps are the unspecified frontmatter-editing mechanism and the lack of a check that the task file was uniquely located before the move.

DimensionReasoningScore

Conciseness

The body is lean — inputs, four numbered steps, and edge cases — with no explanation of concepts Claude already knows; every token earns its place. There is nothing to trim that would move it off the top anchor.

5 / 5

Actionability

Concrete `find`, `mkdir -p`, and `mv` commands plus a real example invocation make the guidance mostly executable, but step 2 gives no concrete mechanism for editing the frontmatter and `<OLD_PRIORITY>` is never explicitly determined, keeping it below fully copy-paste-ready.

4 / 5

Workflow Clarity

The find → update → move → report sequence is clear and the Important section supplies checkpoints (missing-args guard, already-at-priority guard, done/ guard). It falls short of a 5 because there is no validation that `find` located exactly one task file before moving it; the operation is a single-file move, so the destructive/batch cap at 3 does not apply.

4 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with well-organized sections (Inputs / Steps / Important) and no need for external reference files — per the rubric's simple-skill note, this earns the top score.

5 / 5

Total

18

/

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, and clearly identifies its devflow niche, but it omits any 'when to use' trigger guidance. Adding a 'Use when...' clause with natural trigger phrases (e.g., changing a task's priority, moving a task between P0-P4) would substantially improve it.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user wants to change a task's priority, move a task between P0-P4 folders, or reprioritize the devflow backlog.'

Include natural synonyms users would say — 'change priority', 'move task', 'promote/demote' — to broaden trigger-term coverage.

Briefly enumerate what the skill touches (priority frontmatter field, tasks/<PRIORITY>/ folder layout) to sharpen the 'what' beyond two actions.

DimensionReasoningScore

Specificity

Names the domain ('devflow task') and exactly two concrete actions ('move between priority folders (P0-P4)' and 'update frontmatter'), which matches the anchor for 1-2 concrete actions without comprehensive coverage; it does not list the several actions needed for a 4.

3 / 5

Completeness

The 'what' is clear (reprioritize, move between folders, update frontmatter) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like 'reprioritize', 'priority', and 'P0-P4' are relevant, but common natural variations users would say ('change priority', 'move a task', 'promote/demote') are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'devflow task' carves a clear niche with minimal conflict risk against generic skills, but sibling devflow task skills (create/update/complete) could overlap and no explicit triggers distinguish them, placing it between anchors 4 and 5.

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

devflow-plugin/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.