agent-sparc-coordinator

Agent skill for sparc-coordinator - invoke with $agent-sparc-coordinator

1.24x

Quality

—

Does it follow best practices?

Impact

98%

1.24x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body presents a well-structured overview of the SPARC methodology and its phase/gate workflow, but it is largely abstract and descriptive rather than actionable, padded with generic content, and contains a stray duplicate config block. It reads more like a methodology summary than executable skill guidance.

Suggestions

Add concrete, executable guidance: actual commands or code for invoking/spawning the specialized SPARC agents and for executing each phase, instead of bullet-list activity descriptions.

Define the quality gates as concrete validation steps with feedback loops (what to check, how, and what to do on failure) rather than abstract pass criteria.

Remove the stray duplicate YAML/hook block (lines 6-29) and trim generic restatements of well-known concepts to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is organized into sections but padded with generic bullets restating concepts Claude already knows (e.g. 'Detailed requirements gathering', 'TDD implementation', 'Integration testing') plus a stray duplicate YAML/hook block; it is mostly efficient but could be tightened considerably.	2 / 3
Actionability	Almost everything is abstract description rather than instruction: phases are listed as bullet activities, 'Usage Examples' are natural-language prompts, and there is no executable code or concrete command for actually running the orchestration — matching the 'describes rather than instructs' anchor.	1 / 3
Workflow Clarity	A clear phase-transition sequence with five named quality gates is present (ASCII diagram), but the gates are abstract criteria ('All requirements documented') with no concrete validation steps or error-recovery feedback loops, leaving validation gaps.	2 / 3
Progressive Disclosure	Content is well-organized into headers but is a single ~155-line monolithic file with no bundle files or external references; several sections (phase detail, integration patterns) are inline material that could be split out.	2 / 3
	Total	7 / 12 Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is largely a placeholder label: it identifies the skill by name but says nothing concrete about what it does or when to use it, with no explicit trigger guidance. It is too vague to function as an effective skill description.

Suggestions

Replace the label with concrete actions the skill performs, e.g. 'Orchestrates the SPARC methodology — coordinates Specification, Pseudocode, Architecture, Refinement, and Completion phases with quality gates.'

Add an explicit 'Use when...' trigger clause, e.g. 'Use when applying the SPARC methodology or coordinating multi-phase development workflows.'

Include natural trigger terms users would say (e.g. 'SPARC methodology', 'phase coordination', 'quality gates') rather than only the invocation syntax '$agent-sparc-coordinator'.

Dimension	Reasoning	Score
Specificity	The description 'Agent skill for sparc-coordinator - invoke with $agent-sparc-coordinator' names no concrete actions at all; it only labels the artifact as an 'agent skill' for a named coordinator, matching the vague/abstract anchor 'Helps with documents'.	1 / 3
Completeness	The 'what' is very weak (only 'Agent skill for sparc-coordinator', with no stated actions) and the 'when' is entirely missing — there is no 'Use when...' clause, so it falls into the 'missing what OR when, or both very weak' anchor.	1 / 3
Trigger Term Quality	'sparc-coordinator' is a relevant keyword a SPARC-methodology user would say, but 'invoke with $agent-sparc-coordinator' is invocation syntax rather than a natural trigger term, and common variations (e.g. 'SPARC methodology', 'phase coordination') are missing.	2 / 3
Distinctiveness Conflict Risk	The SPARC methodology niche is somewhat specific and unlikely to broadly conflict, but the description provides no distinct triggers, so it could still overlap with other coordination/orchestration skills.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: 8ae8752

Reviewed: 2 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.