backend-testing
Write comprehensive backend tests including unit tests, integration tests, and API tests. Use when testing REST APIs, database operations, authentication flows, or business logic. Handles Jest, Pytest, Mocha, testing strategies, mocking, and test coverage.
79
71%
Does it follow best practices?
Impact
96%
1.21xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/backend-testing/SKILL.mdQuality
Discovery
100%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 a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes a clear 'Use when...' clause with natural trigger terms, and carves out a distinct niche for backend testing that differentiates it from other potential testing or coding skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'unit tests, integration tests, and API tests' and specific domains: 'REST APIs, database operations, authentication flows, business logic'. Also names specific tools: 'Jest, Pytest, Mocha, mocking, test coverage'. | 3 / 3 |
Completeness | Clearly answers both what ('Write comprehensive backend tests including unit tests, integration tests, and API tests') AND when ('Use when testing REST APIs, database operations, authentication flows, or business logic') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'backend tests', 'unit tests', 'integration tests', 'API tests', 'REST APIs', 'database operations', 'authentication', 'Jest', 'Pytest', 'Mocha', 'mocking', 'test coverage'. These are all terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on backend testing specifically, with distinct triggers like 'REST APIs', 'database operations', 'authentication flows', and specific testing frameworks. Unlikely to conflict with frontend testing or general coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent, actionable code examples for backend testing across multiple frameworks, but is severely bloated with explanatory content Claude doesn't need. The document reads like a tutorial or documentation page rather than a concise skill file, with unnecessary sections like metadata, version info, learning resources, and extensive explanations of basic concepts.
Suggestions
Remove the metadata section, version info, related skills, tags, and external learning resources - these don't belong in a skill file
Cut explanatory text about concepts Claude knows (TDD definition, why test isolation matters, what AAA pattern is) and keep only the actionable patterns
Extract the Python/FastAPI example to a separate PYTEST_EXAMPLES.md file and reference it from the main skill
Add explicit validation steps like 'Run tests before committing: npm test && npm run test:coverage' with failure recovery guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 600+ lines with extensive explanations Claude already knows (what TDD is, AAA pattern basics, why test isolation matters). Includes metadata, version info, learning resources, and book recommendations that don't belong in a skill file. | 1 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for Jest, Pytest, Supertest with complete test files, configuration, and setup scripts. All examples are concrete and runnable. | 3 / 3 |
Workflow Clarity | Steps are listed (1-5) but lack explicit validation checkpoints. No feedback loops for when tests fail or coverage is insufficient. The workflow is more of a tutorial structure than a clear process with verification steps. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. No references to external files for detailed examples or API references. The 'References' section links to external learning resources rather than organizing content across skill files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (845 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.