agent-code-goal-planner

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

2.28x

Quality

13%

Does it follow best practices?

Impact

89%

2.28x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-code-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 description is essentially a label and invocation command with no substantive content. It fails on every dimension: it does not describe what the skill does, when to use it, or provide any natural trigger terms. 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., 'Breaks down coding goals into step-by-step implementation plans, identifies required files and dependencies, and generates task lists for complex code changes.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to plan a coding task, break down a feature into steps, create an implementation roadmap, or organize a complex code change.'

Remove the invocation syntax from the description (or move it to a separate field) and replace it with user-facing language that explains the skill's purpose and scope.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for code-goal-planner' is entirely abstract 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 the skill's name and invocation command, providing no functional or contextual information.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. 'code-goal-planner' is an internal tool name, not a term users would naturally use in requests. The invocation syntax '$agent-code-goal-planner' is technical jargon.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could overlap with any code-related skill. 'Code-goal-planner' gives a hint of domain but is not specific enough to distinguish it from other planning, coding, or goal-setting skills.	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 extremely verbose and repetitive, explaining the same SPARC-GOAP integration concept multiple times through different lenses (YAML, TypeScript, JavaScript, bash) without adding proportional value. It reads more like a methodology whitepaper than an actionable skill — much of the content describes planning frameworks Claude already understands rather than providing specific, executable guidance. The lack of progressive disclosure means all ~350+ lines load into context regardless of the task complexity.

Suggestions

Reduce content by 60-70%: Remove redundant explanations of SPARC phases (currently explained 3+ times), generic software metrics Claude already knows, and the 'Core Competencies' list which is purely descriptive.

Split into multiple files: Move the detailed YAML planning patterns, metrics framework, and SPARC mode descriptions into separate referenced files, keeping SKILL.md as a concise overview with one clear example.

Add validation checkpoints: Include explicit 'verify before proceeding' steps between SPARC phases, such as checking that specification deliverables exist before starting architecture, to prevent cascading failures.

Make code examples truly executable: Replace the illustrative TypeScript interfaces and JavaScript class stubs with actual working commands or scripts that produce real output, or clearly mark them as templates.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Massive amounts of content that Claude already knows (what GOAP is, what sprint planning is, basic git branching, generic software metrics like p99 latency targets). Multiple redundant sections repeat the same SPARC phases. The SPARC-GOAP synergy section restates what was already covered. Most YAML/code examples are illustrative templates rather than actionable specifics.	1 / 3
Actionability	Contains concrete code examples and CLI commands (npx claude-flow sparc run...), but most are illustrative rather than executable — the TypeScript interfaces, JavaScript classes, and YAML plans are templates/pseudocode showing structure rather than copy-paste-ready implementations. The MCP tool integration section uses a non-standard syntax that isn't clearly executable.	2 / 3
Workflow Clarity	The SPARC phases provide a clear sequence (Specification → Pseudocode → Architecture → Refinement → Completion), and the bash example at the end shows numbered steps. However, there are no explicit validation checkpoints or feedback loops for error recovery — no 'if this fails, do X' guidance. The workflow is presented as a happy path without verification steps between phases.	2 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files. Everything is inlined — the YAML plans, code examples, metrics frameworks, risk assessment, and multiple planning patterns are all in one massive document. Content like the metrics framework, risk assessment, and SPARC mode descriptions could easily be split into referenced files.	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.