CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-tasks

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

53

Quality

60%

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 ./.claude/skills/speckit-tasks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 workflow with concrete commands and a strict task format, plus validation checkpoints. Its main weakness is token efficiency: the extension-hooks logic is duplicated near-verbatim across two sections.

Suggestions

De-duplicate the extension-hooks handling: define the YAML parsing, dot-to-hyphen, and output-format rules once and reference them from both the pre- and post-tasks steps to reclaim a substantial token budget.

Add an explicit feedback loop after the format-validation step in the Report (e.g. 'If any task fails format validation, regenerate the offending entries and re-validate') to strengthen workflow clarity.

Consider moving the lengthy Task Generation Rules and hook output templates into a references file linked from the main body to improve progressive disclosure and reduce inline length.

DimensionReasoningScore

Conciseness

Most content is actionable rather than explanatory of basics, but the extension-hooks block (YAML parsing rules, dot-to-hyphen conversion, and full output format templates) is duplicated almost verbatim in both Pre-Execution Checks and step 6, which is a padded section that could be tightened.

3 / 5

Actionability

Concrete commands (e.g. `check-prerequisites.sh --json`), exact file/template paths, and copy-paste-ready checklist format with ✅/❌ examples provide mostly executable guidance; the minor gap is the absence of a full sample tasks.md output.

4 / 5

Workflow Clarity

A clear numbered sequence (Pre-Execution Checks through Report) with validation checkpoints (task completeness validation and a final format-validation confirmation) is present; it stops short of 5 because there is no explicit validate→fix→retry feedback loop for error recovery.

4 / 5

Progressive Disclosure

The body is well organized into clearly headed sections (User Input, Pre-Execution Checks, Outline, Task Generation Rules) with no nested external references; the gap keeping it from 5 is the length and the duplicated hooks detail that could live in a separate reference file.

4 / 5

Total

15

/

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 clearly states what the skill does but omits any 'when to use' trigger guidance, which caps completeness and limits trigger-term quality. It is reasonably specific and distinct within the spec-kit domain.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when breaking a feature spec into an executable task list or when generating tasks.md from spec-kit design artifacts.'

Broaden trigger terms with natural synonyms users would say, such as 'task list', 'work breakdown', or 'turn user stories into tasks'.

List a couple more concrete actions (e.g. derive dependencies, identify parallelizable tasks) to lift specificity from a single action toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (tasks.md generation for a feature) and one concrete action ("Generate an actionable, dependency-ordered tasks.md") with a couple of qualifiers, but does not list several distinct actions, matching the anchor for 1-2 concrete actions rather than the multi-action anchor at 4.

3 / 5

Completeness

The 'what' is clear (generate a dependency-ordered tasks.md) but there is no 'Use when...' clause or equivalent explicit trigger guidance for 'when', which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "tasks.md", "feature", and "design artifacts" appear, but common natural variations or synonyms a user would say (e.g. "task list", "break down stories", "work breakdown") are missing, fitting the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The niche (spec-kit tasks.md generation from design artifacts) is mostly distinct with only minor overlap risk against closely related spec-kit skills like plan or spec generation; it is not a 5 because no explicit distinct trigger phrases are given.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
g14wx/staffSync
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.