agent-planner

Agent skill for planner - invoke with $agent-planner

1.43x

Quality

13%

Does it follow best practices?

Impact

92%

1.43x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-planner/SKILL.md

Quality

Content

27%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 skill is overly verbose, spending significant tokens on generic project management concepts that Claude already understands (task decomposition, risk assessment, best practices). The MCP tool integration examples and YAML output format are the strongest parts, providing concrete, actionable guidance. The skill would benefit greatly from aggressive trimming of generic advice and better structural organization.

Suggestions

Remove the 'Best Practices', 'Collaboration Guidelines', and 'Core Responsibilities' sections entirely — these are generic concepts Claude already knows. Focus the skill on the specific output format and MCP tool calls.

Add validation checkpoints to the planning workflow: e.g., 'After generating the plan YAML, verify all dependency task-ids exist, check for circular dependencies, and confirm all referenced agents are available.'

Extract the MCP tool integration examples and YAML output format into separate reference files (e.g., MCP_TOOLS.md, OUTPUT_FORMAT.md) and reference them from a concise overview.

Consolidate the Planning Process section into a brief numbered list with only the non-obvious, skill-specific steps rather than restating standard planning methodology.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanation of concepts Claude already knows (task decomposition, dependency analysis, risk assessment). The 'Best Practices' and 'Collaboration Guidelines' sections are generic project management advice that adds no actionable value. The skill could be reduced to ~30% of its current size.	1 / 3
Actionability	The MCP tool integration section provides concrete code examples with specific tool calls, and the YAML output format is well-defined. However, much of the content is abstract guidance ('Analyze the complete scope of the request', 'Identify key objectives') rather than executable instructions. The JavaScript examples use a specific MCP API which is helpful but the overall planning process remains vague.	2 / 3
Workflow Clarity	The 5-step planning process is clearly sequenced, and the output format provides structure. However, there are no validation checkpoints or feedback loops — no guidance on what to do if a plan fails validation, how to verify plan quality, or when to re-plan. For a coordination agent that orchestrates potentially destructive or complex operations, this is a significant gap.	2 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no bundle files to support it. Everything is inlined — the YAML output format, MCP examples, best practices, and collaboration guidelines could all be split into separate reference files. For a skill this long (~120+ lines of content), the lack of structure across files is a clear weakness.	1 / 3
	Total	6 / 12 Passed

Description

0%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 an extremely weak description that provides virtually no useful information for skill selection. It fails on every dimension: it names no concrete actions, includes no natural trigger terms, answers neither 'what' nor 'when', and is so generic it would be indistinguishable from many other potential skills. The description reads more like a label than a functional description.

Suggestions

Describe what the planner actually does with specific concrete actions (e.g., 'Creates structured project plans, breaks down complex tasks into subtasks, estimates timelines, and tracks dependencies').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks to plan a project, break down a task, create a roadmap, organize work, or needs help with task prioritization').

Remove the invocation command ('$agent-planner') from the description as it wastes space that should be used for capability and trigger information, and replace with domain-specific keywords that distinguish this skill from other potentially similar skills.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for planner' is entirely vague and abstract, giving no indication of what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	The only keyword is 'planner', which is generic and not a natural term users would use in a request. The description includes an invocation command ('$agent-planner') but no natural language trigger terms.	1 / 3
Distinctiveness Conflict Risk	'Planner' is extremely generic and could conflict with any skill involving planning, project management, task organization, scheduling, or strategic thinking. There are no distinct triggers to differentiate it.	1 / 3
	Total	4 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Path: .agents/skills/agent-planner/SKILL.md
Commit: 913f9ea

Reviewed: 3 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.