agent-tester
Agent skill for tester - invoke with $agent-tester
26
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
0%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 to use it, or what domain it operates in. The only content is a generic label and an invocation command, making it impossible for Claude to appropriately select this skill.
Suggestions
Add specific concrete actions describing what this skill does (e.g., 'Runs unit tests, generates test cases, validates code coverage').
Include a 'Use when...' clause with explicit trigger conditions (e.g., 'Use when the user asks to test code, run tests, or validate functionality').
Add natural keywords users would actually say when needing this skill (e.g., 'unit tests', 'test suite', 'QA', 'test coverage', specific testing frameworks).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for tester' is completely abstract with no indication of 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 'Use when...' clause and no explanation of functionality. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is '$agent-tester' which is a technical invocation command, not a natural keyword users would say. 'Tester' is too generic to be useful. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'tester' is extremely generic and could conflict with any testing-related skill. There are no distinct triggers to differentiate this 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 testing tutorial rather than actionable agent instructions. It explains fundamental testing concepts Claude already understands (test pyramid, TDD, AAA pattern) while lacking project-specific workflows and clear task sequences. The content would benefit from dramatic reduction and restructuring around specific testing workflows with validation checkpoints.
Suggestions
Remove explanations of basic testing concepts (test pyramid, TDD, mocking basics) and focus on project-specific patterns and tool configurations
Add a clear workflow section with numbered steps: 1) Analyze code to test, 2) Identify test types needed, 3) Write tests, 4) Run and validate, 5) Report results via memory
Split detailed code examples into separate reference files (UNIT-EXAMPLES.md, INTEGRATION-EXAMPLES.md) and keep only essential patterns in the main skill
Add explicit validation checkpoints, especially for when tests fail - what should the agent do next?
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive code examples that explain basic testing concepts Claude already knows (test pyramid, AAA pattern, mocking). The 300+ lines could be reduced to essential project-specific patterns and tool configurations. | 1 / 3 |
Actionability | Contains executable code examples for various test types, but they are generic templates rather than project-specific guidance. The MCP tool integration examples are concrete but the overall guidance is more educational than immediately actionable. | 2 / 3 |
Workflow Clarity | No clear workflow sequence for how to approach testing tasks. Lists test types and best practices but lacks step-by-step process with validation checkpoints. Missing guidance on when to run which tests or how to handle test failures. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including detailed code examples that could be split into separate reference files (e.g., EXAMPLES.md, SECURITY-TESTS.md). | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%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.
- Reviewed
Table of Contents
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.