agent-coder

Agent skill for coder - invoke with $agent-coder

1.12x

Quality

13%

Does it follow best practices?

Impact

79%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-coder/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 is an extremely weak description that provides essentially no useful information about the skill's capabilities or when it should be used. It reads more like a label or invocation instruction than a functional description. It fails on every dimension of the rubric.

Suggestions

Replace the entire description with concrete actions the skill performs (e.g., 'Writes, debugs, and refactors code across multiple languages, creates new files, and implements features').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks to write code, fix bugs, implement features, refactor functions, or create new source files').

Remove the invocation syntax ('invoke with $agent-coder') from the description and focus entirely on capabilities and trigger conditions that help Claude select this skill appropriately.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for coder' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of capabilities.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'coder', which is overly generic. There are no natural keywords a user would say when needing a specific coding task performed. The invocation syntax '$agent-coder' is not a natural trigger term.	1 / 3
Distinctiveness Conflict Risk	'Coder' is extremely generic and would conflict with virtually any coding-related skill. There is nothing to distinguish this from other programming or development skills.	1 / 3
	Total	4 / 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 a generic software engineering best practices document that teaches Claude things it already knows (SOLID principles, DRY, error handling patterns, security basics, testing guidelines). It lacks project-specific context that would make it valuable, and the MCP tool integration section—while more unique—is buried in a wall of general advice. The content would benefit dramatically from being reduced to only the novel, project-specific information (MCP coordination patterns, specific tool invocations) with generic coding advice removed entirely.

Suggestions

Remove all generic software engineering advice (SOLID, DRY, KISS, YAGNI, security basics, testing best practices, code style) that Claude already knows—this could cut 70%+ of the content.

Focus the skill on what's unique: MCP memory coordination patterns, the specific agent collaboration protocol, and the pre/post hook behavior.

Add explicit validation checkpoints to the implementation workflow (e.g., 'Run lint after implementation', 'Verify tests pass before marking complete', 'Store status in memory before handoff').

Split MCP tool integration and collaboration protocols into a separate reference file, keeping SKILL.md as a concise overview with links.

Dimension	Reasoning	Score
Conciseness	Extremely verbose - explains basic concepts Claude already knows (SOLID, DRY, KISS, YAGNI, single responsibility, dependency injection, error handling patterns, file organization conventions, security basics like 'never hardcode secrets'). Most of this is generic software engineering knowledge that wastes tokens.	1 / 3
Actionability	Contains some concrete TypeScript code examples and MCP tool invocations, but much of the guidance is generic advice rather than project-specific executable instructions. The code examples are illustrative patterns rather than copy-paste-ready solutions for specific tasks.	2 / 3
Workflow Clarity	The 'Implementation Process' section lists steps (understand requirements, design first, TDD, incremental implementation) but lacks validation checkpoints, feedback loops, or explicit verification steps. For a coding agent that modifies files, there's no validate-then-proceed pattern.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline including lengthy code style guidelines, best practices, file organization, documentation patterns, and MCP tool examples that could be split into separate reference files.	1 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Commit: 398f7c2

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