agent-sparc-coordinator
Agent skill for sparc-coordinator - invoke with $agent-sparc-coordinator
39
6%
Does it follow best practices?
Impact
98%
1.24xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-sparc-coordinator/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 weak description that fails on every dimension. It provides no information about what the skill does, when it should be used, or what triggers should activate it. It reads more like a label than a functional description, making it essentially useless for skill selection among multiple options.
Suggestions
Add concrete actions describing what sparc-coordinator actually does (e.g., 'Orchestrates multi-step tasks by breaking them into subtasks and coordinating execution across agents').
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 coordinate complex workflows, decompose tasks, or manage multi-agent collaboration').
Remove the invocation syntax ('invoke with $agent-sparc-coordinator') from the description—this is implementation detail, not selection criteria—and replace it with capability and domain information.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for sparc-coordinator' is entirely vague—it doesn't describe what the skill does, only names itself. There are no verbs describing capabilities. | 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 trigger information. | 1 / 3 |
Trigger Term Quality | The only potentially relevant term is 'sparc-coordinator', which is technical jargon unlikely to be used naturally by users. There are no natural keywords a user would say when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic ('Agent skill for sparc-coordinator') that it provides no distinguishing characteristics. Without knowing what it does, it could conflict with any coordination or orchestration 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 as a high-level methodology overview document rather than an actionable skill for Claude. It describes what SPARC is and what its phases contain conceptually, but provides zero concrete instructions on how to actually execute any phase, invoke any agent, or validate any quality gate. The content is heavily padded with abstract descriptions of concepts Claude already understands.
Suggestions
Replace abstract phase descriptions with concrete, executable instructions: specific commands to invoke each agent, exact quality gate validation steps, and actual tool calls rather than conceptual descriptions.
Cut at least 60% of the content by removing explanations of well-known concepts (TDD, requirements gathering, integration testing) and focusing only on project-specific conventions and tool invocations.
Add concrete examples with actual input/output: show what a quality gate check looks like in practice, what memory_store/memory_search calls to make, and what specific artifacts each phase produces.
Split detailed agent descriptions, integration patterns, and metrics into separate reference files, keeping SKILL.md as a concise orchestration guide with clear cross-references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows (what SPARC phases are, what quality gates mean, what TDD is). Most content is abstract description rather than actionable instruction. The skill is ~150 lines of high-level descriptions that could be condensed to ~30 lines of concrete guidance. | 1 / 3 |
Actionability | Almost entirely abstract and descriptive with no executable code, no concrete commands, no specific tool invocations, and no copy-paste ready examples. 'Usage Examples' are just natural language prompts, not actual implementation steps. There's no guidance on how to actually invoke agents, run quality gates, or execute any of the described workflows. | 1 / 3 |
Workflow Clarity | The phase transition diagram and quality gates provide a clear sequence, but there are no concrete validation steps, no actual commands to run at each gate, and no feedback loops for error recovery. The workflow is conceptual rather than operational. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline regardless of depth or relevance. Sections like 'Memory Integration', 'Success Metrics', and detailed agent descriptions could be split into separate reference files. No navigation aids or cross-references. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%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/claude-flow
- Commit
f547cec
- 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.