CtrlK
BlogDocsLog inGet started
Tessl Logo

add-task

creates draft task file in .specs/tasks/draft/ with original user intent

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/sdd/skills/add-task/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-structured, actionable single-purpose skill with clear sequencing and verification. Its main weakness is an internal contradiction about the target directory (todo/ vs draft/) and some redundancy across the output, criteria, and examples sections.

Suggestions

Fix the directory contradiction: step 5 instructs writing to .specs/tasks/todo/ while constraints and examples mandate .specs/tasks/draft/ — pick one (draft/) and align all references.

Collapse the three near-identical example blocks into one template plus a compact table of type-specific filename variations to reduce redundancy.

Add an explicit validate-and-retry note (e.g. if the filename is not unique, append a numeric suffix and re-check) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean instructional content with no padding of concepts Claude already knows; the only trimmable excess is three near-identical example blocks and some overlap between Expected Output and Success Criteria, fitting the efficient-with-minor-trim anchor.

4 / 5

Actionability

It provides a concrete bash command, file-naming rules, a copy-paste Write template, and typed examples, but step 5 says to write to .specs/tasks/todo/ while constraints, expected output, and examples say draft/, a concrete contradiction that leaves a minor executability gap.

4 / 5

Workflow Clarity

Five numbered steps are clearly sequenced with a uniqueness-verification checkpoint and a script fallback, but there is no explicit error-recovery loop after validation, matching clear-sequence-with-minor-validation-gaps.

4 / 5

Progressive Disclosure

Content is well organized into labeled sections (Role, Goal, Input, Instructions, Constraints, Expected Output, Success Criteria, Examples) with one-level references and no nested chains, though the referenced create-folders.sh is not part of the bundle.

4 / 5

Total

16

/

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 states a clear, location-specific action but is a single-purpose sentence with no trigger guidance. It is distinct within its plugin niche yet lacks the "when to use" context that would raise its completeness.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when the user asks to create, add, or draft a new task/spec."

Include common synonyms a user might say ("task", "spec", "todo item") to improve trigger term coverage.

Briefly enumerate the key outputs (title, type classification, dependencies) to lift specificity beyond one action.

DimensionReasoningScore

Specificity

Names a concrete action ("creates draft task file") and a specific location (".specs/tasks/draft/") plus "original user intent", but covers only one main action rather than a comprehensive list, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

The description gives a clear "what" (creates a draft task file in .specs/tasks/draft/ preserving user intent) but has no "Use when..." or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "task file" and the spec path appear, but natural user phrasings (e.g. "add a task", "create a spec") and synonyms are missing, fitting the anchor for some relevant keywords without common variations.

3 / 5

Distinctiveness Conflict Risk

The unique .specs/tasks/draft/ path and draft-creation purpose make it mostly distinct from other skills, with only minor overlap risk against related spec-workflow skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NeoLabHQ/context-engineering-kit
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.