testing
Use when writing or running tests for this project. Covers unit vs E2E test decisions, test file locations, mock patterns, and project-specific testing conventions. (project)
66
79%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/testing/SKILL.mdQuality
Discovery
67%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 competent description that clearly states when to use the skill and covers the testing domain adequately. Its main weaknesses are that it describes categories of knowledge rather than concrete actions, and it could include more natural trigger terms that users would use when asking about testing. The explicit 'Use when...' clause is a strong point.
Suggestions
Replace category labels with concrete actions, e.g., 'Creates and runs unit and E2E tests, sets up mocks, determines test file placement, and enforces project-specific testing conventions.'
Add more natural trigger term variations such as 'test suite,' 'spec files,' 'test coverage,' 'integration tests,' or framework-specific terms like 'jest,' 'vitest,' 'pytest' if applicable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (testing) and mentions some specific areas like 'unit vs E2E test decisions, test file locations, mock patterns, and project-specific testing conventions,' but these are categories rather than concrete actions (e.g., it doesn't say 'creates test files,' 'generates mocks,' or 'runs test suites'). | 2 / 3 |
Completeness | Clearly answers both 'what' (covers unit vs E2E test decisions, test file locations, mock patterns, testing conventions) and 'when' (explicitly states 'Use when writing or running tests for this project'). | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'tests,' 'unit,' 'E2E,' 'mock,' and 'testing conventions,' which users might naturally say. However, it misses common variations like 'test suite,' 'jest,' 'pytest,' 'spec files,' 'integration tests,' 'test coverage,' or 'TDD.' | 2 / 3 |
Distinctiveness Conflict Risk | The testing focus is reasonably distinct, but 'project-specific testing conventions' is broad and could overlap with general coding style or project convention skills. The '(project)' tag helps scope it, but the description could conflict with a general coding standards skill. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted testing skill that delivers project-specific conventions efficiently. It excels at actionability with exact commands, file paths, code examples, and a clear decision table. The content respects Claude's intelligence by focusing exclusively on project-specific details rather than explaining general testing concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what testing is, what vitest is, or other concepts Claude already knows. Every section delivers project-specific information (paths, commands, patterns, known issues) without padding. | 3 / 3 |
Actionability | Provides exact commands for running tests, concrete code examples for writing E2E tests, specific file paths, and a clear decision table for choosing test types. Everything is copy-paste ready and project-specific. | 3 / 3 |
Workflow Clarity | The 'Running Tests During Development' section provides a clear 3-step sequence with rationale. The decision table clearly guides which test type to use. The E2E test example shows the complete setup/execution pattern. For a testing conventions skill, the workflow is appropriately scoped. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but it's all inline in one file. The reference to `superpowers:test-driven-development` is good, but some content like the full E2E patterns or mock patterns could potentially be split out. However, the total length is reasonable enough that this is a minor issue. | 2 / 3 |
Total | 11 / 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.
- Repository
- cloudflare/sandbox-sdk
- Commit
3b58a22
- 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.