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 description is essentially a label with an invocation command, providing zero information about the skill's purpose, capabilities, or appropriate usage context. It fails on every dimension because it describes neither what the skill does nor when it should be selected. A user or Claude would have no basis for choosing this skill over any other.
Suggestions
Add concrete actions describing what sparc-coordinator actually does (e.g., 'Coordinates multi-step task decomposition across sub-agents, manages workflow orchestration, and synthesizes 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 complex tasks into subtasks, coordinate multiple agents, or orchestrate multi-step workflows').
Remove the invocation instruction ('invoke with $agent-sparc-coordinator') from the description—this is operational metadata, not selection criteria, 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 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 contextual information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'sparc-coordinator', which is technical jargon that a user would not naturally say. There are no natural language trigger terms that would help Claude match user requests to this skill. | 1 / 3 |
Distinctiveness Conflict Risk | While 'sparc-coordinator' is a unique name, the description 'Agent skill' is so generic it provides no meaningful differentiation. Without knowing what it does, it could conflict with any agent-related 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 conceptual overview of the SPARC methodology rather than an actionable skill for Claude. It is extremely verbose, explaining obvious concepts at length while providing no concrete, executable guidance. The content would benefit enormously from being condensed to essential coordination logic with specific commands, concrete quality gate checks, and actual examples of phase inputs/outputs.
Suggestions
Replace abstract phase descriptions with concrete, executable steps: specify exact commands to run, files to create, and validation checks to perform at each quality gate.
Cut at least 60% of the content by removing explanations of concepts Claude already knows (TDD, what documentation is, what testing means) and keeping only project-specific instructions.
Add concrete examples with actual inputs and expected outputs for at least one complete SPARC cycle, showing exactly what artifacts are produced at each phase.
Split detailed content (integration patterns, memory integration, best practices) into separate referenced files and keep SKILL.md as a concise overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already knows (what SPARC phases are, what quality gates mean, what TDD is). The content is heavily padded with abstract descriptions, lists of obvious items ('Edge case identification', 'Complexity analysis'), and sections like 'Success Metrics' that add no actionable value. Most of this could be cut by 70%+ without losing useful information. | 1 / 3 |
Actionability | Almost entirely abstract and descriptive rather than instructive. No executable code, no concrete commands, no specific examples with inputs/outputs. The 'Usage Examples' section contains only vague one-line descriptions like 'Use SPARC methodology to develop a user authentication system' with no actual implementation guidance. The workflow diagram is ASCII art showing phase names, not actionable steps. | 1 / 3 |
Workflow Clarity | The phase sequence is clearly defined and quality gates are listed between phases, which provides some structure. However, the quality gates lack concrete validation criteria (e.g., 'All requirements documented' is vague), there are no explicit feedback loops for when gates fail, and no specific commands or checks to actually enforce the gates. The workflow is more of a conceptual framework than an executable process. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files despite the content being long enough to warrant splitting. Sections like 'Memory Integration', 'Integration Patterns', 'Best Practices', and detailed phase descriptions could all be separate files. No bundle files exist to support progressive disclosure, and the skill doesn't reference any external resources. | 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
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.