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 known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-planner/SKILL.md

Quality

Content

27%

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 planning concepts and best practices that Claude already understands. While it provides some useful concrete elements (YAML output format, MCP tool examples), the majority of the content is abstract guidance that doesn't add actionable value. The lack of validation checkpoints and the monolithic structure further weaken its effectiveness.

Suggestions

Cut the 'Core Responsibilities', 'Best Practices', and 'Collaboration Guidelines' sections entirely — these describe generic planning concepts Claude already knows. Focus on the specific output format and MCP tool integration.

Add explicit validation steps: how to verify a plan is complete (e.g., check all tasks have dependencies mapped, verify no circular dependencies, confirm all agents referenced exist).

Extract the MCP tool examples and YAML output format into a separate reference file, keeping SKILL.md as a concise overview with clear pointers.

Replace abstract instructions like 'Analyze the complete scope of the request' with concrete decision criteria or checklists specific to this system's capabilities.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanation of generic planning concepts Claude already knows (task decomposition, dependency analysis, risk assessment). The 'Best Practices' and 'Collaboration Guidelines' sections are generic advice that add no specific value. The content could be reduced by 60%+ without losing actionable information.	1 / 3
Actionability	The MCP tool integration section provides concrete code examples with specific tool calls, and the YAML output format is a useful template. 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 unclear syntax (not standard MCP invocation patterns).	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 planning 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. All content — from basic responsibilities to MCP tool examples to best practices — is inlined in a single long document with no clear navigation or layering.	1 / 3
	Total	6 / 12 Passed

Description

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, lacks both 'what' and 'when' guidance, and is so generic it would be indistinguishable from many other potential skills.

Suggestions

Describe what the planner actually does with specific actions (e.g., 'Creates step-by-step execution plans for complex multi-step tasks, breaks down goals into subtasks, and tracks progress').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user needs to break down a complex task, create a project plan, organize steps, or coordinate multiple subtasks').

Clarify the specific niche this planner fills to distinguish it from other planning-related skills (e.g., is it for project planning, task decomposition, agent orchestration, etc.).

Dimension	Reasoning	Score
Specificity	The description contains 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	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of capabilities.	1 / 3
Trigger Term Quality	The only keyword is 'planner', which is generic and not a natural term users would say when needing planning help. The invocation command '$agent-planner' is technical syntax, not a natural trigger term.	1 / 3
Distinctiveness Conflict Risk	'Planner' is extremely generic and could conflict with any skill involving planning, scheduling, project management, task organization, 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
Commit: 28c81c0

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.