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 description is critically deficient across all dimensions. It provides no information about what the skill does, when it should be used, or what domain it operates in. The only content is a generic label ('agent skill for tester') and an invocation command, which is insufficient for Claude to make informed skill selection decisions.

Suggestions

Replace the entire description with concrete actions the skill performs, e.g., 'Runs unit tests, generates test cases, and validates code 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 reduce conflict risk, e.g., mention specific testing frameworks, languages, or types of testing (unit, integration, end-to-end).

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for tester' is extremely vague and does not describe what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	The only potentially useful trigger term is 'tester' and '$agent-tester', but these are not natural keywords a user would say when needing a specific capability. There are no domain-specific or action-oriented keywords.	1 / 3
Distinctiveness Conflict Risk	The term 'tester' is extremely generic and could conflict with any testing-related skill. There is nothing to distinguish this skill's niche or purpose from other potential 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 is a generic testing textbook rather than an actionable agent skill. It explains concepts Claude already knows (test pyramid, FIRST principles, common testing patterns) at great length, consuming significant token budget without adding novel, project-specific value. The lack of a clear workflow, validation steps, and progressive disclosure makes it poorly suited as an agent instruction document.

Suggestions

Reduce content to ~50 lines focusing only on project-specific testing conventions, tool configurations, and MCP coordination patterns that Claude wouldn't already know.

Add a clear step-by-step workflow: e.g., 1) Identify what to test, 2) Write tests, 3) Run tests with specific command, 4) Validate coverage meets threshold, 5) Report results via MCP, 6) If failures, fix and re-run.

Remove generic testing education (test pyramid, FIRST principles, AAA pattern, basic best practices) and replace with project-specific constraints and patterns.

Split detailed examples (security testing, performance testing, E2E patterns) into separate referenced files if they're needed, keeping SKILL.md as a concise overview.

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 lists universally known testing advice.	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-JSON syntax that isn't valid code. Missing key details like how to actually run tests or which specific framework to use in context.	2 / 3
Workflow Clarity	No clear workflow sequence for how to actually perform testing tasks. Lists test types and examples but doesn't define a step-by-step process for when/how to write tests, run them, interpret results, and iterate. No validation checkpoints or feedback loops for the testing process itself.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline including lengthy code examples for unit, integration, E2E, performance, and security testing. No bundle files exist, yet the content is far too long to justify being a single file—content should be split into separate reference files.	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: ca77f83

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.