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

Discovery

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.

Suggestions

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

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to plan a project, create a roadmap, break down work, or organize tasks').

Remove the invocation syntax ('invoke with $agent-planner') from the description and replace it with domain-specific language that distinguishes this skill from other potentially similar skills.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for planner' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. 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 say when needing planning help. The invocation syntax '$agent-planner' is technical jargon, not a user 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 similar domains. There is nothing to distinguish it.	1 / 3
	Total	4 / 12 Passed

Implementation

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 significantly over-engineered and verbose, spending most of its tokens teaching Claude concepts it already knows (how to plan, what dependencies are, what risk assessment means). The MCP tool integration section provides the only genuinely novel, actionable content. The skill would benefit enormously from being reduced to the YAML output format template, the MCP tool examples, and a brief set of constraints specific to this system.

Suggestions

Remove the 'Core Responsibilities', 'Best Practices', and 'Collaboration Guidelines' sections entirely — these describe general planning concepts Claude already knows.

Condense the 'Planning Process' section to a brief checklist focused on what's unique to this system (e.g., which agents exist, what MCP tools to use), not generic planning steps.

Add explicit validation checkpoints: e.g., 'After decomposition, verify all tasks have clear inputs/outputs and assigned agents before storing the plan to memory.'

Extract the MCP tool examples and YAML output format into referenced files, keeping SKILL.md as a concise overview with navigation links.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanation of planning concepts Claude already understands (task decomposition, dependency analysis, risk assessment). The 'Best Practices' and 'Core Responsibilities' sections are largely restating obvious planning principles. 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 a specific MCP API which adds some concreteness.	2 / 3
Workflow Clarity	The 5-step planning process is sequenced but lacks validation checkpoints or feedback loops. There's no explicit step for validating the plan before execution, no error recovery guidance, and no mechanism to verify that task decomposition is complete or correct before proceeding to resource allocation.	2 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files. Everything from high-level philosophy to MCP tool examples is inlined in a single document. The planning process, output format, collaboration guidelines, best practices, and MCP integration could each be separate referenced documents.	1 / 3
	Total	6 / 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/ruflo
Commit: 398f7c2

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.