agent-agent
Agent skill for agent - invoke with $agent-agent
33
0%
Does it follow best practices?
Impact
93%
4.65xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-agent/SKILL.mdQuality
Discovery
0%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 skill 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. It appears to be a placeholder or auto-generated stub rather than a meaningful description.
Suggestions
Replace the entire description with concrete actions the skill performs (e.g., 'Spawns sub-agents to parallelize complex tasks, delegates subtasks, 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 needs to break down a complex task into parallel subtasks or coordinate multiple agents').
Differentiate this skill from other potentially similar skills by specifying its unique niche, such as the types of tasks it handles or the specific agent orchestration patterns it supports.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for agent' is entirely abstract and vague, 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 description 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 task done. The invocation syntax '$agent-agent' is not a natural trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'agent' is extremely generic and could conflict with virtually any agent-related skill. There is nothing distinctive about this description to differentiate it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%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-style document that reads more like a product brochure than actionable instructions for Claude. It contains hundreds of lines of non-executable pseudocode with undefined dependencies, explains well-known CS concepts Claude already understands, and lacks any clear workflow with validation checkpoints. The content would need to be reduced by 80%+ and rewritten with truly executable examples and clear step-by-step guidance.
Suggestions
Reduce content to under 100 lines focusing on the specific MCP tool names, their exact calling conventions, and 1-2 complete executable examples showing a real planning workflow end-to-end.
Remove all explanations of well-known concepts (GOAP, A*, PageRank, behavior trees, utility theory) and instead provide only the project-specific tool integration details Claude needs.
Add a clear numbered workflow with explicit validation checkpoints, e.g., 'After building the action graph, verify the matrix analysis returns valid properties before proceeding to optimization.'
Extract advanced topics (multi-agent coordination, gaming AI, learning from execution) into separate referenced files, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 500+ lines. Explains concepts Claude already knows (what GOAP is, what A* search is, what behavior trees are, what PageRank does). Massive amounts of illustrative pseudocode that isn't truly executable. The introductory paragraph restates the description. Bullet-point lists of capabilities read like marketing copy rather than 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 (underscores vs hyphens). The code is elaborate pseudocode dressed up as real code, not copy-paste ready guidance. | 1 / 3 |
Workflow Clarity | There is no clear sequential workflow with validation checkpoints. The numbered sections (1-5) present disconnected code blocks rather than a coherent step-by-step process. There are no explicit validation steps, no error recovery feedback loops in the main workflow, and no guidance on when to verify intermediate results. The 'Dynamic Replanning' section describes an OODA loop conceptually but doesn't provide actionable validation steps. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no bundle files to support it. Everything is inlined in a single massive document. Content that could be separated (gaming AI integration, multi-agent coordination, advanced configuration) is all dumped into one file with no navigation structure beyond markdown headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
90%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
- Commit
9d4a9ea
- Reviewed
Table of Contents
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.