agent-sparc-coordinator
Agent skill for sparc-coordinator - invoke with $agent-sparc-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-sparc-coordinator25
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 critically deficient across all dimensions. It functions only as a label with an invocation command, providing zero information about capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what sparc-coordinator actually does (e.g., 'Coordinates multi-agent workflows, delegates subtasks, manages parallel execution').
Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when orchestrating complex tasks, breaking down large problems, or coordinating multiple agents').
Define the specific domain or problem space this skill addresses to distinguish it from other agent-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for sparc-coordinator' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no explanation of purpose or use cases. | 1 / 3 |
Trigger Term Quality | The only terms present are 'agent skill', 'sparc-coordinator', and the invocation command. These are technical jargon, not natural keywords a user would say when needing this functionality. | 1 / 3 |
Distinctiveness Conflict Risk | While 'sparc-coordinator' is a specific name, the description provides no context about what domain or tasks it handles, making it impossible to distinguish from other skills based on user intent. | 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 like a methodology overview document rather than actionable agent instructions. It extensively describes what SPARC is and its phases but provides no concrete commands, executable code, or specific implementation guidance. The content is verbose, abstract, and lacks the practical details Claude would need to actually orchestrate SPARC workflows.
Suggestions
Replace abstract phase descriptions with concrete commands or code snippets that Claude should execute for each phase (e.g., specific prompts to send to sub-agents, file operations, validation commands)
Add executable examples showing actual agent invocation syntax, expected inputs/outputs, and error handling patterns
Remove explanatory content about what SPARC methodology is - focus only on how to execute it
Extract detailed phase content to separate reference files and keep SKILL.md as a concise quick-start with clear navigation to details
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already knows (what SPARC phases are, what quality gates mean, basic workflow concepts). The content is heavily padded with organizational structure that adds little actionable value. | 1 / 3 |
Actionability | Almost entirely abstract descriptions with no executable code, commands, or concrete implementation details. Usage examples are vague prompts rather than actual instructions. The 'workflow' diagram is ASCII art, not actionable steps. | 1 / 3 |
Workflow Clarity | Phase transitions are listed and quality gates are named, but there are no concrete validation steps, no actual commands to execute, 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 despite being lengthy. No clear navigation structure or signposted references to detailed materials. | 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.
- 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.