task-decomposition
Breaks down complex software, writing, or research tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns. Use when the user asks to plan a project, decompose a feature, create subtasks, split up work, or needs help organizing a large piece of work into a step-by-step plan. Triggered by phrases like "break down", "decompose", "where do I start", "too big", "split into tasks", "work breakdown", or "task list".
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It clearly specifies what the skill does (task decomposition with dependency graphs and milestones), when to use it (explicit 'Use when' clause), and includes a rich set of natural trigger phrases. The description is well-structured, uses third person voice, and is specific enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'breaks down complex tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns.' This describes concrete outputs (dependency graphs, milestone breakdowns) and specific domains (software, writing, research). | 3 / 3 |
Completeness | Clearly answers both 'what' (breaks down complex tasks into atomic units with dependency graphs and milestones) and 'when' (explicit 'Use when...' clause plus a 'Triggered by phrases like...' section with concrete trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'break down', 'decompose', 'where do I start', 'too big', 'split into tasks', 'work breakdown', 'task list', 'plan a project', 'create subtasks'. These are highly natural phrases a user would actually use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around task decomposition and work breakdown planning. The specific focus on dependency graphs, atomic units, and milestone breakdowns distinguishes it from generic project management or coding skills. Trigger terms like 'work breakdown' and 'decompose' are distinctive. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that provides clear decomposition techniques with concrete examples and a reusable task template. Its main strengths are the variety of decomposition approaches, the dependency management workflow, and the verification checklist. Minor weaknesses include some unnecessary explanatory text, a referenced EXAMPLES.md that doesn't exist in the bundle, and cross-skill references that lack proper links.
Suggestions
Trim the introductory text under 'Core Principle' — Claude doesn't need motivation about why small tasks are better; just state the constraints (few hours, clear done criteria).
Either provide the referenced EXAMPLES.md in the bundle or remove the reference to avoid a broken progressive disclosure chain.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of structured examples, but includes some unnecessary framing ('If a task feels too big, it is too big') and slightly verbose descriptions of concepts Claude already understands (e.g., explaining what 'atomic' and 'independent' mean). The decomposition techniques section is well-structured but could be tighter. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready templates including the task template with markdown checkboxes, dependency graph notation, phased ordering, and four distinct decomposition techniques with specific examples. The decomposition checklist and task template are immediately usable. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: choose a decomposition technique → apply the task template → map dependencies → order into phases → verify with the checklist. The dependency management section provides explicit phasing, and the checklist serves as a validation checkpoint. For a planning/decomposition skill (non-destructive), this level of workflow clarity is appropriate. | 3 / 3 |
Progressive Disclosure | References EXAMPLES.md for detailed worked examples (good signal), but EXAMPLES.md is not provided in the bundle. References to other skills (design-first, verification-gates, testing/red-green-refactor) are mentioned but not linked. The content is reasonably well-organized but the inline examples are somewhat lengthy and could potentially be offloaded. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- rohitg00/skillkit
- Commit
a9e5c83
- 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.