agent-goal-planner

Agent skill for goal-planner - invoke with $agent-goal-planner

1.42x

Quality

Does it follow best practices?

Impact

87%

1.42x

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-goal-planner/SKILL.md

Quality

Content

12%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 reads as a high-level description of GOAP concepts rather than an actionable skill that teaches Claude how to do something specific. It extensively explains well-known AI planning concepts (A*, OODA, preconditions/effects) that Claude already understands, while providing almost no concrete, executable guidance. The MCP examples are syntactically questionable and lack context for when and how to use them.

Suggestions

Remove all conceptual explanations of GOAP, A*, and OODA loops — Claude already knows these. Replace with specific instructions for how to apply planning to the user's request.

Provide concrete, executable examples showing a complete planning cycle: a specific initial state, goal state, action inventory, generated plan, and expected output format.

Replace the pseudo-JavaScript MCP examples with actual tool invocation syntax that Claude can copy-paste, including realistic parameters and expected responses.

Add validation checkpoints to the workflow, such as how to verify a plan is valid before execution, how to detect failure conditions, and specific criteria for triggering replanning.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and padded with concepts Claude already knows. The lengthy descriptions of GOAP, A* search, OODA loops, precondition analysis, and effect prediction are all well-known concepts that don't need explanation. The bullet-point lists of 'core capabilities' read like a resume rather than actionable instructions. Most of the content could be removed without losing any practical value.	1 / 3
Actionability	The skill provides no concrete, executable guidance. The MCP integration examples use JavaScript syntax that isn't valid tool invocation format, and the GOAP methodology section describes abstract concepts ('Use A* pathfinding to search through possible action sequences') rather than giving specific instructions Claude can follow. There are no real examples of inputs, outputs, or actual planning workflows.	1 / 3
Workflow Clarity	The five-step planning methodology (State Assessment → Action Analysis → Plan Generation → Execution Monitoring → Dynamic Replanning) provides a clear sequence, and the OODA loop sub-steps add some structure. However, there are no validation checkpoints, no error recovery steps, and no concrete criteria for when to replan vs. continue. The workflow is conceptual rather than operational.	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 in a single document with no clear separation between overview and detailed content. For a skill this complex, there should be separate references for action definitions, state modeling patterns, and example plans.	1 / 3
	Total	5 / 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 fails on every dimension. It reads more like an invocation instruction than a skill description, providing no information about what the skill does, when to use it, or what user requests should trigger it. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.

Suggestions

Describe the concrete actions this skill performs (e.g., 'Creates structured goal plans with milestones, breaks down objectives into actionable steps, tracks progress toward goals').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to plan goals, set objectives, create action plans, break down tasks, or define milestones').

Remove the invocation instruction ('invoke with $agent-goal-planner') from the description and replace it with functional content that helps Claude understand the skill's purpose and scope.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for goal-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. The description only states it's an 'agent skill' and how to invoke it, providing no functional or contextual information.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'goal-planner', which is a tool name rather than a natural keyword a user would say. There are no natural trigger terms like 'plan goals', 'set objectives', 'track milestones', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it provides no distinguishing characteristics. 'Agent skill for goal-planner' could overlap with any planning, goal-setting, or task management skill.	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-goal-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.