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

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-goal-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 functions more as an invocation instruction than a skill description. It fails on every dimension: it names no concrete actions, includes no natural trigger terms, provides no 'when to use' guidance, and offers nothing to distinguish it from other skills. It is essentially unusable for skill selection purposes.

Suggestions

Describe specific concrete actions the skill performs, e.g., 'Breaks down high-level goals into actionable steps, creates milestone timelines, and tracks progress toward objectives.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to plan goals, break down objectives, create action plans, set milestones, or organize tasks toward a target outcome.'

Remove the invocation instruction ('invoke with $agent-goal-planner') from the description, as it does not help Claude decide when to select this skill and wastes space that should be used for capability and trigger information.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for goal-planner' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. It provides neither capability details nor usage triggers—only an invocation command.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'goal-planner', which is a technical/internal label rather than a natural keyword a user would say. There are no natural trigger terms like 'plan goals', 'set objectives', 'create milestones', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it provides no distinguishing characteristics. 'Goal-planner' could overlap with any planning, task management, or project-related skill without clear boundaries.	1 / 3
	Total	4 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads like a marketing description or README for a GOAP system rather than an actionable skill file. It explains what GOAP is and lists abstract capabilities but never provides concrete, executable instructions for how Claude should actually perform goal-oriented planning. The MCP integration examples are superficial and the entire document wastes tokens on concepts Claude already understands.

Suggestions

Replace the abstract capability list and methodology description with concrete, executable steps: show actual input/output examples of how to decompose a goal, evaluate actions, and generate a plan.

Provide real, copy-paste-ready MCP tool invocations with realistic parameters and expected responses, not illustrative pseudocode with placeholder values.

Add explicit validation checkpoints to the workflow, e.g., 'After generating a plan, verify all preconditions are satisfiable before execution' with concrete verification steps.

Remove the lengthy 'core capabilities' bullet list and GOAP algorithm explanation—these are textbook concepts that waste tokens. Focus on the specific conventions, formats, and tool patterns Claude should use.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and padded with concepts Claude already knows. The lengthy enumeration of 'core capabilities' (A* search, precondition analysis, effect prediction, etc.) and the detailed GOAP methodology description are textbook explanations that don't add actionable value. The bullet-heavy format wastes tokens on abstract descriptions rather than concrete instructions.	1 / 3
Actionability	The content is almost entirely abstract description rather than executable guidance. The MCP 'examples' are illustrative pseudocode with hardcoded string values, not real executable patterns. There are no concrete steps for how to actually perform goal planning—no real code, no specific commands, no input/output examples showing how a plan is constructed or executed.	1 / 3
Workflow Clarity	While the 5-step methodology and OODA loop are listed, they are abstract descriptions of concepts rather than actionable workflow steps. There are no validation checkpoints, no error recovery procedures, no concrete sequencing of what to actually do. 'Use A* pathfinding to search through possible action sequences' is not an actionable step.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files, no clear navigation structure, and no separation of overview from detailed content. Everything is dumped into a single document with no bundle files to support it. The content that could be split (methodology details, MCP examples, domain modeling) is all inline.	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: 9d4a9ea

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