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

77%

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

The canonical home for this skill is task-complete 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.

A well-crafted, lean instruction-only skill: concrete commands, clear sequencing with a not-found recovery branch, and a report checklist. The only shortfalls are minor — no post-move/status verification and a couple of placeholder-dependent commands.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a one-line context sentence, an Inputs section, five numbered steps with concrete commands, and three Important bullets. It never explains concepts Claude already knows; the only trim candidates are trivial (the '$ARGUMENTS' marker appears in both the Inputs section and at the end, and one Important bullet restates the step-2 ordering as emphasis).

5 / 5

Actionability

Gives executable guidance — 'find ... -name "<TASK_ID>.md" -not -path "*/done/*"', 'mkdir -p .../done', 'mv .../tasks/<priority>/<TASK_ID>.md .../tasks/done/' — plus a retain() template and a report template. Minor gaps keep it below a 5: the mv command relies on a '<priority>' placeholder resolved only implicitly from the find result, and 'retain(...)' is template syntax that assumes the Hindsight tool's exact calling convention.

4 / 5

Workflow Clarity

A clear five-step sequence (find → update status → move → retain → report) with an explicit error-recovery branch ('If not found, check if it's already in done/ and inform the user') and a report template that doubles as a completion checklist. It is a single reversible file move rather than a destructive/batch operation, so no cap applies, but there is no verification that the frontmatter edit or the mv actually succeeded.

4 / 5

Progressive Disclosure

A self-contained, single-purpose skill (~55 lines) with clean section structure (Inputs, Steps, Important) and no external references — none are needed at this size, and the inline commands and templates are appropriately placed. Per the simple-skill guidance, well-organized sections with no nested or buried references earn the top score.

5 / 5

Total

18

/

20

Passed

Description

58%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.

A specific, third-person description that clearly states what the skill does, with good distinctiveness from other skills. Its main weakness is the absence of any 'when to use' trigger guidance and of common trigger synonyms beyond "done".

Suggestions

Add an explicit 'Use when...' clause, e.g. "Use when the user says a devflow task is done, complete, or finished" — this directly addresses the missing trigger guidance capping completeness at 3.

Include natural trigger synonyms such as "complete", "finish", or "close out" alongside "done" so the description matches how users actually phrase the request (trigger_term_quality).

Optionally mention that the skill locates the task file and reports completion, closing the minor coverage gap in specificity.

DimensionReasoningScore

Specificity

"update status, move to done/ folder, and retain learnings" names the devflow domain and three concrete actions, matching the 'several specific actions; minor gaps' anchor. It falls short of a 5 because the workflow's other actions (finding the task file, reporting completion) go unmentioned.

4 / 5

Completeness

The 'what' is clear and concrete (mark done, update status, move to done/, retain learnings), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is above a 2 because the 'what' is fully explicit, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ("devflow task", "done", "status", "learnings") but common natural variations are missing — users would equally say "complete", "finish", or "close out" a task, and none appear. This matches the 'some relevant keywords but missing common variations or synonyms' anchor rather than the good-coverage anchor above.

3 / 5

Distinctiveness Conflict Risk

"devflow task" and "done/ folder" pin a clear niche with distinct triggers, so conflict risk is low. It sits at 'mostly distinct; minor overlap risk' rather than a 5 because task-completion phrasing ("mark a task as done") could plausibly collide with other generic task-management skills.

4 / 5

Total

14

/

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