planner
Create structured plans for multi-task projects that can be executed by the task-orchestrator skill. Use when breaking down complex work into parallel/sequential tasks with dependencies.
90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 description is functional with good completeness and distinctiveness, clearly stating both purpose and trigger conditions. However, it could benefit from more specific action verbs and additional natural trigger terms that users might actually say when needing this skill.
Suggestions
Add more concrete actions like 'define task dependencies', 'specify execution order', 'identify parallelizable work'
Include additional natural trigger terms users might say: 'project planning', 'workflow', 'coordinate tasks', 'task breakdown'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (multi-task projects, plans) and mentions some actions (create structured plans, breaking down work), but doesn't list comprehensive concrete actions like 'define dependencies', 'set task priorities', or 'generate execution order'. | 2 / 3 |
Completeness | Clearly answers both what ('Create structured plans for multi-task projects that can be executed by the task-orchestrator skill') and when ('Use when breaking down complex work into parallel/sequential tasks with dependencies') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms ('multi-task projects', 'parallel/sequential tasks', 'dependencies') but misses common user phrases like 'project planning', 'task breakdown', 'workflow', 'orchestrate', or 'coordinate tasks'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche with distinct triggers - specifically mentions 'task-orchestrator skill', 'parallel/sequential tasks', and 'dependencies' which creates a unique identity unlikely to conflict with general planning or project management skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%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 skill that efficiently communicates a complex planning methodology. It excels at providing concrete, actionable guidance through the bad/good examples and detailed template, while maintaining excellent organization with clear phase progression and appropriate file references for detailed prompts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete examples (bad vs good task breakdown), a complete plan template with specific fields, and exact commands for execution. The template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-phase process with explicit steps, validation built into the sprint structure (demo/validation checklists), and acceptance criteria requirements for each task. The workflow includes feedback loops through subagent review. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear references to detailed prompts in separate files (prompts/planner.md, prompts/parallel-task.md). Content is appropriately split between quick start, principles, template, and execution. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.