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 fails on every dimension. It reads more like a label or invocation instruction than a functional description. It provides no information about what the skill does, when it should be used, or what distinguishes it from other skills.

Suggestions

Add concrete actions describing what the goal-planner does, e.g., 'Creates structured goal hierarchies, breaks down objectives into actionable steps, and tracks progress toward milestones.'

Add an explicit 'Use when...' clause with natural trigger terms, 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 decide when to select this skill.

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 keyword is 'goal-planner' which is a tool name, not a natural term a user would say. There are no natural language 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

Implementation

12%

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

This skill reads more like a persona description or marketing document than an actionable skill file. It extensively describes abstract AI planning concepts (GOAP, A*, OODA) that Claude already understands, while providing almost no concrete, executable guidance on what to actually do when invoked. The MCP examples are the only semi-concrete content but are incomplete and not truly executable.

Suggestions

Replace the abstract capability list and methodology description with concrete, executable workflows showing exactly how to decompose a goal, evaluate actions, and produce a plan output format.

Add a concrete example showing input (a goal description) and expected output (a structured plan with specific format/schema) so Claude knows exactly what to produce.

Remove explanations of well-known concepts (A*, OODA loops, precondition analysis) and replace with specific constraints, output formats, and decision criteria unique to this skill.

Either make the MCP integration examples fully executable with real tool call syntax, or remove them and replace with actual tool usage patterns that Claude can copy-paste.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanation of concepts Claude already knows (A* search, OODA loops, precondition analysis). The bullet-point capability list and methodology sections describe abstract concepts rather than providing actionable instructions. Most of the content is padding that doesn't teach Claude anything new.	1 / 3
Actionability	The content is almost entirely abstract description rather than concrete guidance. The MCP integration examples are pseudocode-like snippets with JavaScript syntax that aren't executable (e.g., JSON.stringify in what appears to be a tool invocation). There are no concrete steps for how to actually perform GOAP planning in practice.	1 / 3
Workflow Clarity	The 5-step planning methodology provides a clear sequence (State Assessment → Action Analysis → Plan Generation → Execution Monitoring → Dynamic Replanning), but there are no validation checkpoints, no error recovery steps, and no concrete examples of what each step actually produces. The OODA loop is mentioned but not operationalized.	2 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files for detailed information. Everything is inline with no clear navigation structure. The capability list, methodology, and examples are all dumped into a single document with no progressive structure.	1 / 3
	Total	5 / 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: 3d8f171

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.