CtrlK
BlogDocsLog inGet started
Tessl Logo

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

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 well-structured, actionable skill that provides concrete decomposition techniques with clear examples and a reusable task template. Its main strengths are the variety of decomposition approaches, the dependency management section with visual graph notation, and the verification checklist. Minor weaknesses include some unnecessary explanatory text that Claude doesn't need and a reference to EXAMPLES.md that doesn't exist in the bundle.

Suggestions

Trim the 'Core Principle' section — Claude doesn't need motivational framing about why decomposition matters; jump straight to the techniques.

Provide the referenced EXAMPLES.md file in the bundle, or remove the reference if it doesn't exist.

DimensionReasoningScore

Conciseness

The content is mostly efficient with good use of structured examples, but includes some unnecessary explanation (e.g., 'If a task feels too big, it is too big' and the elaboration on what a well-decomposed task should be are things Claude already understands). The decomposition techniques section is well-structured but could be slightly tighter.

2 / 3

Actionability

Provides concrete, copy-paste-ready templates (task template with markdown format), specific examples for each decomposition technique, a dependency graph notation, phased ordering, and a verification checklist. The guidance is specific and directly usable.

3 / 3

Workflow Clarity

The workflow is clearly sequenced: choose a decomposition technique, apply the task template to each unit, map dependencies, order into phases, and verify with the checklist. The decomposition checklist serves as an explicit validation checkpoint. For a planning/decomposition skill (non-destructive), this level of workflow clarity is excellent.

3 / 3

Progressive Disclosure

References EXAMPLES.md for detailed worked examples, which is good progressive disclosure. However, EXAMPLES.md is not provided in the bundle, making the reference unverifiable. The cross-references to other skills (design-first, verification-gates, testing/red-green-refactor) are helpful but the main content is somewhat long and could benefit from splitting the task template and dependency management into separate reference files.

2 / 3

Total

10

/

12

Passed

Description

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 concise yet comprehensive, uses third person voice correctly, and carves out a distinct niche.

DimensionReasoningScore

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 mention of dependency graphs, atomic units, and milestone breakdowns distinguishes it from generic project management or planning skills. The trigger phrases are distinctive and unlikely to conflict with other skills.

3 / 3

Total

12

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
rohitg00/skillkit
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.