agent-tester

Agent skill for tester - invoke with $agent-tester

1.14x

Quality

Does it follow best practices?

Impact

88%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-tester/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 virtually no useful information. It fails on every dimension: it doesn't describe what the skill does, when to use it, or include any meaningful trigger terms. It reads more like a placeholder label than a functional skill description.

Suggestions

Replace the entire description with concrete actions the skill performs (e.g., 'Runs unit tests, generates test cases, validates test coverage for Python projects').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks to run tests, write test cases, check test coverage, or debug failing tests').

Specify the domain or technology scope to make the skill distinctive (e.g., what kind of testing, what languages/frameworks, what types of artifacts it works with).

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for tester' 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. The description provides no functional information and no trigger guidance.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'tester', which is extremely generic. There are no natural keywords a user would say to invoke this skill beyond the explicit command '$agent-tester'.	1 / 3
Distinctiveness Conflict Risk	The term 'tester' is extremely generic and could overlap with any testing-related skill. There is nothing distinctive about this description to differentiate it from other skills.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

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 generic testing textbook rather than actionable agent instructions. It explains concepts Claude already knows (test pyramid, TDD, AAA pattern, edge cases) at great length while lacking a concrete workflow for how the agent should operate when invoked. The MCP tool integration section adds some project-specific value but uses unclear syntax, and the overall content would benefit enormously from being reduced to ~50 lines of specific, actionable guidance.

Suggestions

Replace the generic testing tutorial with a concise workflow: detect test framework → analyze code changes → write targeted tests → run tests → validate coverage → report results via MCP memory.

Remove explanations of basic testing concepts (test pyramid, FIRST principles, AAA pattern) that Claude already knows, and focus on project-specific conventions and tool usage.

Add explicit validation checkpoints: e.g., 'Run tests after writing → check coverage thresholds → if below threshold, add more tests → only report success when all criteria met.'

Extract the lengthy code examples into a separate EXAMPLES.md file and keep SKILL.md as a lean operational guide under 80 lines.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~250+ lines. Explains basic testing concepts Claude already knows (test pyramid, FIRST principles, AAA pattern, what unit/integration/E2E tests are). The test examples are generic textbook patterns, not project-specific guidance. The best practices section restates well-known testing principles.	1 / 3
Actionability	Contains executable TypeScript test examples which is good, but they are generic templates not tied to any specific project or codebase. The MCP tool integration section uses pseudo-JavaScript syntax that isn't clearly executable. Missing concrete commands for running tests or generating coverage reports.	2 / 3
Workflow Clarity	No clear sequential workflow for how the tester agent should actually operate when invoked. Lists responsibilities and test types but doesn't define a step-by-step process: what to check first, how to decide which tests to write, when to validate, or how to report back. No validation checkpoints or feedback loops for the testing process itself.	1 / 3
Progressive Disclosure	Monolithic wall of text with everything inline. No references to external files, no separation of concerns. Generic test examples, coverage metrics, security tests, performance tests, and MCP integration are all crammed into one file with no navigation structure or layering.	1 / 3
	Total	5 / 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/claude-flow
Commit: 9d4a9ea

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