sparc-methodology

SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration

1.38x

Quality

17%

Does it follow best practices?

Impact

90%

1.38x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/sparc-methodology/SKILL.md

Quality

Discovery

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 relies heavily on methodology jargon and an unexplained acronym without describing concrete actions or providing trigger guidance. It fails to communicate what Claude actually does with this skill or when it should be selected, making it nearly useless for skill selection among multiple options.

Suggestions

Replace the SPARC acronym expansion with concrete actions Claude performs, e.g., 'Breaks down complex projects into specifications, designs architecture, implements iteratively'

Add an explicit 'Use when...' clause with natural trigger terms like 'large project', 'complex feature', 'project planning', 'architecture design', 'iterative development'

Remove or explain 'multi-agent orchestration' - either describe what this means in practical terms or remove the jargon entirely

Dimension	Reasoning	Score
Specificity	The description uses abstract methodology terms (Specification, Pseudocode, Architecture, Refinement, Completion) and jargon ('multi-agent orchestration') without describing any concrete actions Claude would perform.	1 / 3
Completeness	Only vaguely addresses 'what' through methodology buzzwords, and completely lacks any 'when' guidance or 'Use when...' clause. Users cannot determine when this skill should be selected.	1 / 3
Trigger Term Quality	Contains technical jargon like 'SPARC', 'multi-agent orchestration', and methodology acronyms that users would not naturally say when seeking help. No common user-facing keywords are present.	1 / 3
Distinctiveness Conflict Risk	The SPARC acronym and 'multi-agent orchestration' provide some distinctiveness, but 'comprehensive development methodology' is generic enough to potentially conflict with other development-related skills.	2 / 3
	Total	5 / 12 Passed

Implementation

27%

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

This skill is extremely comprehensive but severely over-engineered for a SKILL.md file. It reads more like complete product documentation than actionable guidance for Claude. The content explains many concepts Claude already understands (TDD cycles, microservices patterns, testing strategies) and could be reduced by 70-80% while improving usability.

Suggestions

Reduce to a 50-100 line overview with quick-start examples, moving detailed mode descriptions to a separate MODES_REFERENCE.md file

Remove explanations of concepts Claude already knows (what TDD is, what microservices are, testing strategies) and focus only on tool-specific syntax and patterns

Add explicit validation steps to workflows (e.g., 'Verify swarm initialized successfully before spawning agents')

Split integration examples and common workflows into separate EXAMPLES.md and WORKFLOWS.md files with clear one-level-deep references

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 800+ lines with extensive repetition. Explains concepts Claude already knows (what TDD is, what microservices are, basic testing concepts). Many sections could be condensed to 10% of their current length.	1 / 3
Actionability	Provides concrete code examples and commands that are copy-paste ready, but many examples are pseudocode-like JavaScript objects rather than actual executable code. The MCP tool calls use a non-standard syntax that may not be directly executable.	2 / 3
Workflow Clarity	Multi-step workflows are listed but lack explicit validation checkpoints. The TDD workflow shows steps but doesn't include verification that each step succeeded before proceeding. No error recovery or feedback loops for failed operations.	2 / 3
Progressive Disclosure	Monolithic wall of text with everything inline. No references to external files for detailed content. The table of contents suggests structure but all 800+ lines are in a single file when much could be split into separate reference documents (modes reference, examples, patterns).	1 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1116 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: ruvnet/ruvector
Commit: 462536e

Reviewed: about 12 hours 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.