task-development

Break down skill development into concrete tasks with time estimates, dependencies, and validation criteria. Creates actionable task lists, identifies blockers, estimates effort, and sequences work optimally. Use when planning skill implementation, managing complex builds, or coordinating parallel work.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/task-development/SKILL.md

Quality

Content

60%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-structured, actionable planning skill with clear sequencing and properly signaled one-level references, but it is markedly verbose — heavy redundancy across steps, examples, and quick-reference, plus inline duplication of material that lives in the reference files.

Suggestions

Collapse the three near-identical Examples into one worked example plus a compact comparison table, and remove the Quick Reference section that duplicates Quick Start and Best Practices.

Move the full estimation techniques and dependency-type explanations out of the body into references/estimation-techniques.md and references/dependency-management.md, keeping only a one-line pointer inline.

Trim generic explanations of concepts Claude already knows (three-point formula, critical path, task granularity rationale) to bare rules or links.

Dimension	Reasoning	Score
Conciseness	The ~1270-line body is noticeably verbose: three near-identical example breakdowns, a Quick Reference that duplicates Quick Start/Best Practices content, and inline explanations of concepts Claude already knows (three-point estimation, critical path, dependency types). Not clearly a 1 because the core workflow steps do carry useful guidance.	2 / 5
Actionability	Provides concrete, usable artifacts — a task template, output format spec, dependency-notation tables, sequencing strategies, and executable script invocations ("python scripts/break-down-tasks.py skill-plan.md"). Minor gaps keep it from a 5, e.g. some guidance stays template-shaped rather than fully worked.	4 / 5
Workflow Clarity	Steps 1–6 are clearly sequenced with per-step Objectives, Processes, Outputs, and Examples, plus validation tasks and a Success Criteria checklist. Not a 5 because explicit validate→fix→retry feedback loops are implied rather than spelled out within the steps.	4 / 5
Progressive Disclosure	References are one level deep and clearly signaled via repeated "See Also" links and a References section, with real bundle files (task-breakdown-patterns.md, estimation-techniques.md, dependency-management.md, break-down-tasks.py). Held at 4 because content that belongs in those references (full estimation techniques, dependency types) is duplicated inline.	4 / 5
	Total	14 / 20 Passed

Description

88%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 strong description that clearly states both capabilities and trigger conditions in third person with concrete actions. Trigger-term coverage is good but could add synonyms and concrete artifacts to reach the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Break down skill development into concrete tasks with time estimates, dependencies, and validation criteria", "Creates actionable task lists, identifies blockers, estimates effort, and sequences work optimally" — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both what ("Break down skill development into concrete tasks...") and when ("Use when planning skill implementation, managing complex builds, or coordinating parallel work.") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ("planning skill implementation", "managing complex builds", "coordinating parallel work"), but is missing common synonyms and concrete file/extension triggers that would push it to a 5.	4 / 5
Distinctiveness Conflict Risk	The skill-development task-breakdown niche is fairly distinct with specific triggers, but "planning skill implementation" and "coordinating parallel work" have minor overlap with general project-planning skills.	4 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1272 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
referenced_paths_exist	Referenced path issues: 16 missing	Warning

	Total	13 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/task-development/SKILL.md
Commit: 93ed392

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.