Name: agent-implementer-sparc-coder
Rating: 46.6 (1 reviews)
Author: ruvnet

Blog Docs Log in Get started

agent-implementer-sparc-coder

Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder

1.09x

Quality

26%

Does it follow best practices?

Impact

69%

1.09x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-implementer-sparc-coder/SKILL.md

The canonical home for this skill is agent-implementer-sparc-coder in ruvnet/claude-flow

Quality

Content

48%Weight 40%Scale 1-5

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 clear TDD workflow with verification checkpoints, but is padded with generic software-engineering principles Claude already knows and relies on stub/non-executable code with broken path syntax. It is monolithic with no progressive disclosure via reference files.

Suggestions

Remove the generic-principle sections (Implementation Guidelines DRY/YAGNI/KISS/SOLID, Performance Optimization, Documentation Standards) that Claude already knows; retain only SPARC-specific guidance.

Replace stub comments ('// Implementation', '// Arrange, Act, Assert') with executable code and fix the '$' path separators to '/' (e.g. 'tests/unit/auth.test.js') so examples run as written.

Move large reference-style blocks (Code Patterns, Error Handling Patterns) into separate reference files linked from the overview to reduce the monolithic inline content.

Dimension	Reasoning	Score
Conciseness	The ~226-line body pads several sections with concepts Claude already knows (DRY/YAGNI/KISS/SOLID, 'choose efficient data structures', 'proper indexing', 'pagination') and stub code, matching 'noticeably verbose; several unnecessary padded sections'.	2 / 5
Actionability	Some concrete guidance exists (retry-with-backoff, file structure), but most code is pseudocode with undefined variables (authTestSuite, userModel) and broken '$' path separators instead of '/', matching 'pseudocode instead of executable code; missing key details'.	3 / 5
Workflow Clarity	The Red/Green/Refactor phases are clearly sequenced with verification checkpoints (Bash('npm test') after each phase, plus lint in Refactor); only an explicit 'if failing, fix and retry' feedback loop is missing.	4 / 5
Progressive Disclosure	The file has clear section headers but is a monolithic 226-line document with no bundle files or external references; code patterns, optimization, and error-handling blocks that belong in separate files are all inlined.	3 / 5
	Total	12 / 20 Passed

Description

3%Weight 40%Scale 1-5

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 a meta invocation stub rather than a capability statement: it says how to invoke the skill but not what it does or when to use it. It fails on specificity, trigger terms, and completeness.

Suggestions

Replace the invocation stub with a concrete capability statement, e.g. "Transforms specifications into working code using TDD: writes failing tests, implements minimal code, then refactors for quality".

Add an explicit 'Use when...' trigger clause with natural user phrases such as 'implementing a feature from a spec', 'writing code test-first', or 'refactoring for quality'.

Drop the 'invoke with $...' syntax from the description; it conveys no capability or trigger information.

Dimension	Reasoning	Score
Specificity	The description only states "Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder"; it names a domain but lists zero concrete actions, matching the 'entirely vague; no concrete actions' anchor.	1 / 5
Completeness	Neither 'what' (just 'agent skill for X') nor 'when' (only invoke syntax, no 'Use when...' clause) is meaningfully present; both are extremely vague, matching the lowest anchor.	1 / 5
Trigger Term Quality	It contains only the technical identifier "implementer-sparc-coder" and invocation syntax "$agent-implementer-sparc-coder"; no natural keywords a user would say, matching 'only technical jargon'.	1 / 5
Distinctiveness Conflict Risk	The named identifier narrows it slightly, but the template 'Agent skill for X - invoke with $X' is generic and identical across all such agent skills, giving high overlap risk.	2 / 5
	Total	5 / 20 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/ruflo
Path: .agents/skills/agent-implementer-sparc-coder/SKILL.md
Commit: fa13ee4

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