CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

task-complete

Mark a devflow task as done — update status, move to done/ folder, and retain learnings.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 exemplary lean, single-purpose skill: every step is concrete and executable, sequencing is clear, and structure is tight with zero padding. Its only weakness is a missing post-move verification step to guard against silently overwriting an existing same-named task in done/.

Suggestions

Add a post-move verification step, e.g. check `ls done/<TASK_ID>.md` or guard the `mv` with a test for an existing file in done/ before overwriting it.

Consider verifying the frontmatter status edit (e.g., grep for 'status: done') before moving the file, since a failed edit would leave a mislabeled task in done/.

DimensionReasoningScore

Conciseness

One short framing line ('You are completing a task from the devflow task backlog.') then pure instruction, commands, and templates with no explanations of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Fully executable guidance throughout: a concrete `find` command with the real tasks path, `mkdir -p` + `mv` commands, the exact `status: done` frontmatter edit, a concrete `retain(...)` call, and a copy-ready report template; placeholders like <TASK_ID> are the expected input.

5 / 5

Workflow Clarity

Five clearly sequenced steps with an error-recovery checkpoint for a missing task ('If not found, check if it's already in done/') and an input fallback, but there is no verification after the move (e.g., confirming no same-named file already exists in done/ that `mv` would silently overwrite), fitting 'most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

A short single-file skill (~56 lines) with no bundle files and nothing that belongs in a separate file; well-organized Inputs/Steps/Important sections make navigation trivial, satisfying the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

63%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 does a good job stating what the skill does with three concrete actions, but it omits any 'when to use it' guidance, which caps both completeness and trigger-term quality. Adding an explicit trigger clause with natural synonyms would substantially improve it.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user says a devflow task is done, complete, or finished, or asks to mark/complete a task.'

Include natural synonyms users would actually say — 'complete a task', 'finish a task', 'task is done' — alongside the current 'devflow task' and 'done' terms.

Mention where the task lives (the devflow tasks backlog) so it is distinguishable from generic task-management or TODO skills.

DimensionReasoningScore

Specificity

Lists three concrete, non-overlapping actions ('update status', 'move to done/ folder', 'retain learnings') that comprehensively cover the task-completion lifecycle; matches the anchor for multiple specific concrete actions with comprehensive coverage.

5 / 5

Completeness

The 'what' is clear and concrete, but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains some relevant natural terms ('devflow task', 'done') but misses common variations and synonyms users would say such as 'complete a task' or 'finish a task'; keyword coverage is thin rather than good.

3 / 5

Distinctiveness Conflict Risk

'Mark a devflow task as done' carves out a distinct niche with low conflict risk, though sibling devflow task-management skills (e.g., create/start task) create minor overlap risk, fitting the 'mostly distinct' anchor rather than 'clear niche with minimal conflict'.

4 / 5

Total

15

/

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-complete/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.