planner

Create structured plans for multi-task projects that can be used by the task-orchestrator skill. Use when breaking down complex work into parallel and sequential tasks with dependencies.

Quality

83%

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

Quality

Content

88%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.

The body is a strong, actionable, well-sequenced planning guide with concrete templates and explicit safety boundaries. The only gap is minor verbosity in provenance notes and the absence of external reference files.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence (no 'what is a plan' padding); only minor provenance lines ('Source', 'Adapted from') and the metadata could be trimmed, keeping it just below the fully lean anchor 5.	4 / 5
Actionability	It provides a concrete 5-phase process, explicit bad-vs-good task examples, a copy-paste plan template with labeled fields, and exact hand-off commands, giving fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	Phases 0-4 are explicitly sequenced with a validation checkpoint (Phase 3 subagent review), per-sprint demo/verification checklists, and a Safety Boundaries section; this is a planning skill so the destructive/batch validation cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the skill is self-contained; the single one-level-deep reference to parallel-task is clearly signaled, and sections are well-organized, but no detail files are used to split content.	4 / 5
	Total	18 / 20 Passed

Description

78%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.

The description is well-formed: it states a clear capability and an explicit trigger clause. Its main weakness is specificity, naming one action rather than a list of concrete operations.

Suggestions

Expand specificity by listing 2-3 concrete plan outputs (e.g., 'produce sprint/task breakdowns, dependency graphs, and acceptance criteria') rather than the single 'Create structured plans' action.

Broaden trigger terms with natural synonyms such as 'break down work', 'plan', or 'schedule' alongside the existing phrasing.

Dimension	Reasoning	Score
Specificity	"Create structured plans" names one concrete action, elaborated by "breaking down complex work into parallel and sequential tasks"; it does not list multiple distinct actions, so it sits at the 1-2-action anchor rather than the multi-action anchor 4-5.	3 / 5
Completeness	It explicitly answers both what ("Create structured plans for multi-task projects") and when ("Use when breaking down complex work...") with concrete trigger phrasing, matching the clearly-and-explicitly-both anchor.	5 / 5
Trigger Term Quality	"Use when breaking down complex work into parallel and sequential tasks with dependencies" surfaces several natural phrasings (breaking down, parallel/sequential tasks, dependencies), but omits common synonyms like "plan" or "schedule", so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	The niche (plans consumed by the task-orchestrator skill with parallel/sequential dependencies) is mostly distinct, with only minor overlap risk against general planning skills.	4 / 5
	Total	16 / 20 Passed

Validation

75%

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 — 12 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	12 / 16 Passed

Repository: jdrhyne/agent-skills
Path: skills/planner/SKILL.md
Commit: 439cd3a

Reviewed: 13 days 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.