CtrlK
BlogDocsLog inGet started
Tessl Logo

task-prioritize

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

65

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/task-prioritize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 for reprioritizing tasks. Its main weakness is the lack of explicit validation steps — particularly checking that the task file exists before attempting modifications and verifying the move succeeded. The guard rails (don't move from done, skip if already at priority) are mentioned but not integrated into the step sequence as checkpoints.

Suggestions

Add an explicit validation step after the find command to handle the case where the task file is not found (e.g., 'If no file found, inform the user and stop').

Integrate the 'already at requested priority' check as step 1.5 between finding the file and updating frontmatter, rather than relegating it to the Important section.

DimensionReasoningScore

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 the only slight concern but they're necessary for the specific environment.

3 / 3

Actionability

Provides fully executable bash commands for finding, moving files, and exact YAML frontmatter format to update. The example invocation and output template are concrete and copy-paste ready.

3 / 3

Workflow Clarity

Steps are clearly sequenced (find → update → move → report), but there's no validation checkpoint — e.g., verifying the file was found before proceeding, confirming the frontmatter was correctly updated, or handling the case where the task file doesn't exist. The 'already at requested priority' check is mentioned but not shown as an explicit step in the workflow.

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

Description

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 the skill does, with a clear niche that minimizes conflict risk. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users might say when wanting to reprioritize tasks.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to change a task's priority, bump a task up or down, or move a devflow task between P0-P4 folders.'

Include additional natural trigger terms like 'change priority', 'bump priority', 'move task', 'task priority', or 'reassign priority level'.

DimensionReasoningScore

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 specifying when Claude should select this skill. The 'when' is only implied.

2 / 3

Trigger Term Quality

Includes relevant 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 a clear niche: devflow tasks, P0-P4 priority folders, and frontmatter updates. This is unlikely to conflict with other skills due to the specific domain terminology.

3 / 3

Total

10

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
AndreJorgeLopes/devflow
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.