test
Advanced test implementation command with unit/E2E support, auto-execution, and smart fixing capabilities
78
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
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, effectively using tables and clear sections to document a test command. However, it lacks executable test code examples showing what tests actually look like, and the workflow sections describe processes abstractly rather than providing concrete validation steps or error handling guidance.
Suggestions
Add a concrete example showing actual generated test code (e.g., a sample Jest or Playwright test that would be created for a LoginForm component)
Expand the Smart Fixing section with specific examples of error types and their fixes, rather than just listing categories
Add explicit validation checkpoints in the test implementation flows (e.g., 'Verify test file compiles before running')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for options and targets, avoiding explanations of concepts Claude already knows. Every section serves a clear purpose without padding. | 3 / 3 |
Actionability | Provides concrete command examples and clear option tables, but lacks executable test code examples. The implementation flow describes what happens but doesn't show actual test code that would be generated. | 2 / 3 |
Workflow Clarity | The test implementation flows are listed but lack explicit validation checkpoints. The smart fixing section mentions iteration but doesn't specify what happens on failure beyond 'apply appropriate fixing strategy' - missing concrete error recovery guidance. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections: usage, targets, options, tool priorities, examples, flows, and output. Content is appropriately structured for a command reference without needing external files. | 3 / 3 |
Total | 10 / 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.