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

Content

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 persona description or marketing document rather than an actionable skill file. It extensively explains well-known CS/AI concepts (GOAP, A*, OODA loops) that Claude already understands, while providing no concrete, executable guidance for actually performing goal-oriented planning. The MCP examples appear to be illustrative pseudocode rather than real, usable tool invocations.

Suggestions

Replace the abstract capability descriptions with concrete, executable workflows showing exactly how to formulate a planning problem, define states/actions, and execute a plan using available tools.

Remove explanations of well-known concepts (GOAP, A*, OODA) and instead provide specific templates or schemas for defining world states, actions with preconditions/effects, and goal specifications.

Add real, copy-paste-ready MCP tool invocations with actual parameters and expected outputs, including validation steps to verify plan correctness before execution.

Structure the content as a concise quick-start section with references to separate files for advanced planning patterns, domain-specific examples, and troubleshooting.

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 AI/CS concepts that don't need explanation. The bullet-point lists of 'core capabilities' read like a resume rather than actionable instructions.	1 / 3
Actionability	The content is almost entirely abstract description rather than concrete guidance. The MCP integration examples are illustrative pseudocode with made-up tool calls (not clearly real or executable), and there are no actual executable workflows, real code, or specific commands that Claude could follow to accomplish a planning task.	1 / 3
Workflow Clarity	While a 5-step methodology is listed, the steps are abstract descriptions of GOAP concepts rather than actionable workflow steps with concrete validation checkpoints. There is no feedback loop for error recovery, no validation steps, and no clear sequence of actual operations to perform.	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 inline with no bundle files to support it.	1 / 3
	Total	4 / 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 reads more like an internal label or invocation instruction than a functional description. It fails on every dimension by lacking concrete actions, natural trigger terms, explicit 'when to use' guidance, and distinguishing details.

Suggestions

Add concrete actions describing what the skill does, 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 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	The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command, with no explanation of capabilities or trigger conditions.	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 'goals', 'planning', 'milestones', 'objectives', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it provides no clear niche. 'Goal-planner' could overlap with any planning, task management, or project-related skill, and there are no distinguishing details.	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/ruflo
Commit: cc8830d

Reviewed: 2 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.