CtrlK
BlogDocsLog inGet started
Tessl Logo

iikit-05-tasks

Generate dependency-ordered task breakdown from plan and specification. Use when breaking features into implementable tasks, planning sprints, or creating work items with parallel markers.

82

1.74x
Quality

88%

Does it follow best practices?

Impact

82%

1.74x

Average score across 14 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

The canonical home for this skill is tessl-labs/intent-integrity-kit

SKILL.md
Quality
Evals
Security

Quality

Content

85%Scale 1-3

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-crafted, complex workflow skill that provides highly actionable guidance with concrete commands, clear sequencing, and proper validation checkpoints. The progressive disclosure is excellent with well-signaled references to supporting documents. The main area for improvement is minor verbosity from repeated bash/powershell dual-platform commands and some sections that could be slightly more compact.

DimensionReasoningScore

Conciseness

The skill is fairly efficient and doesn't over-explain basic concepts, but some sections could be tightened. The long file paths are repeated multiple times (bash/powershell variants), and some instructions like the traceability correct/wrong examples add bulk. However, most content is necessary given the complexity of the workflow.

2 / 3

Actionability

Highly actionable with exact script paths, concrete task format examples (both correct and wrong), specific bash/powershell commands, commit message format, and clear output format. The examples section with correct vs wrong patterns is particularly useful for Claude to follow precisely.

3 / 3

Workflow Clarity

Excellent multi-step workflow with clear sequencing from prerequisites check through execution, validation, writing, committing, and dashboard refresh. Includes explicit validation checkpoints (dependency graph validation with circular dependency detection, plan readiness validation), error handling (ERROR/STOP conditions), and a semantic diff re-run flow with confirmation before overwriting.

3 / 3

Progressive Disclosure

Well-structured with clear references to external files (constitution-loading.md, checklist-gate.md, formatting-guide.md, tasks-template.md, conversation-guide.md, model-recommendations.md) that are all one level deep and clearly signaled with descriptive context. The main skill serves as a clear orchestration overview without inlining content that belongs elsewhere.

3 / 3

Total

11

/

12

Passed

Description

92%Scale 1-3

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 a strong description that clearly communicates both what the skill does and when to use it. The specific mention of dependency ordering and parallel markers provides good differentiation. Minor weakness is potential overlap with broader project planning or sprint management skills.

DimensionReasoningScore

Specificity

Lists specific concrete actions: 'Generate dependency-ordered task breakdown', working from 'plan and specification', creating 'work items with parallel markers'. These are concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers both what ('Generate dependency-ordered task breakdown from plan and specification') and when ('Use when breaking features into implementable tasks, planning sprints, or creating work items with parallel markers').

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'task breakdown', 'features', 'implementable tasks', 'planning sprints', 'work items', 'parallel markers'. These cover common variations of how users would describe this need.

3 / 3

Distinctiveness Conflict Risk

While 'dependency-ordered task breakdown' and 'parallel markers' are fairly distinctive, there could be overlap with general project planning or task management skills. The mention of 'planning sprints' is somewhat generic and could conflict with broader agile/project management skills.

2 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
JaviMontano/jm-adk
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.