agent-agent

Agent skill for agent - invoke with $agent-agent

4.65x

Quality

Does it follow best practices?

Impact

93%

4.65x

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

Quality

Content

0%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 is an extremely verbose, marketing-heavy document that explains well-known CS concepts (GOAP, A*, PageRank, behavior trees) that Claude already understands, while providing no truly executable code. The massive code examples are pseudocode with undefined dependencies, inconsistent MCP tool naming, and no validation steps. It reads more like a product brochure or academic overview than an actionable skill instruction.

Suggestions

Reduce to under 100 lines by removing explanations of concepts Claude already knows (GOAP, A*, PageRank, behavior trees, utility theory) and focus only on the specific MCP tool invocations and their correct parameters.

Make code examples truly executable by defining all referenced helper functions, using consistent and correct MCP tool naming conventions, and providing complete, copy-paste-ready examples.

Add explicit validation checkpoints to the workflow (e.g., 'Verify matrix analysis output contains expected properties before proceeding to PageRank step').

Split content into separate files: keep SKILL.md as a concise overview with references to detailed files like EXAMPLES.md, MULTI-AGENT.md, and ADVANCED-CONFIG.md.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 500+ lines. Explains concepts Claude already knows (GOAP, A*, behavior trees, PageRank, utility theory). Massive amounts of illustrative pseudocode that isn't truly executable. The marketing-style descriptions ('cutting edge of AI-driven objective achievement') waste tokens. Much of this content describes general CS concepts rather than providing novel, actionable instructions.	1 / 3
Actionability	Despite the volume of code, almost none of it is executable. Functions reference undefined helpers (buildConsensusMatrix, generatePreferenceVector, canTransition, stateKey, etc.), classes extend undefined base classes (GOAPAgent), and MCP tool calls use inconsistent naming (mcp__claude_flow__ vs mcp__flow_nexus__ vs mcp__sublinear_time_solver__ with underscores vs hyphens). The code is elaborate pseudocode dressed up as real implementations.	1 / 3
Workflow Clarity	While numbered steps exist (1-5 in the Workflow section), they describe abstract algorithmic concepts rather than a clear operational workflow. There are no validation checkpoints, no error recovery feedback loops in the main workflow, and no clear sequence of 'do this, then verify, then proceed.' The dynamic replanning section describes concepts but doesn't provide actionable verification steps.	1 / 3
Progressive Disclosure	Monolithic wall of text with no bundle files and no references to external documents. Everything is inlined in a single massive file. Content that could be separated (gaming AI integration, multi-agent coordination, advanced configuration) is all dumped into one document with no navigation structure beyond headers.	1 / 3
	Total	4 / 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 poor description that provides essentially no useful information. It fails on every dimension: it describes no concrete actions, includes no natural trigger terms, answers neither 'what' nor 'when', and is completely indistinguishable from any other agent-related skill.

Suggestions

Replace the entire description with concrete actions the skill performs (e.g., 'Delegates subtasks to a sub-agent for parallel execution, manages agent coordination, and aggregates results').

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when the user requests multi-step task delegation, parallel processing, or sub-agent orchestration').

Differentiate this skill from other potential agent-related skills by specifying its unique niche, such as the type of agent, the domain it operates in, or the specific workflow it supports.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for agent' is entirely vague and abstract, providing no information about what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	The only keyword is 'agent', which is overly generic and not a natural term a user would say when needing a specific capability. The invocation syntax '$agent-agent' is not a natural trigger term.	1 / 3
Distinctiveness Conflict Risk	The description is maximally generic — 'agent skill for agent' could conflict with virtually any other agent-related skill and provides no distinguishing characteristics.	1 / 3
	Total	4 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (821 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: ruvnet/claude-flow
Path: .agents/skills/agent-agent/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.