testgen
Generate tests with expert routing, framework detection, and auto-TaskCreate. Triggers on: generate tests, write tests, testgen, create test file, add test coverage.
90
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
89%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 solid skill description with excellent trigger term coverage and clear completeness through the explicit 'Triggers on:' clause. The main weakness is that the capabilities section uses somewhat abstract terms ('expert routing', 'auto-TaskCreate') rather than concrete user-facing actions. The description effectively distinguishes itself from other skills.
Suggestions
Replace abstract terms like 'expert routing' and 'auto-TaskCreate' with concrete actions users care about, e.g., 'Generate unit tests, integration tests, and test suites for multiple frameworks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (test generation) and mentions some actions (framework detection, auto-TaskCreate, routing), but doesn't list concrete specific actions like 'create unit tests, generate integration tests, mock dependencies'. | 2 / 3 |
Completeness | Clearly answers both what (generate tests with expert routing, framework detection, auto-TaskCreate) and when (explicit 'Triggers on:' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'generate tests', 'write tests', 'testgen', 'create test file', 'add test coverage'. These are practical phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on test generation with distinct triggers like 'testgen', 'test coverage', 'create test file'. Unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and clear workflow sequencing. The architecture diagram effectively communicates the multi-step process, and the concrete bash commands make it immediately executable. Minor verbosity in the expert routing details section and some redundancy between the architecture overview and execution steps prevent a perfect conciseness score.
Suggestions
Consolidate the Expert Routing Details section with the Step 4 routing table to eliminate redundancy - the bullet points largely repeat what the table already shows
Remove the CLI Tool Integration table's 'Purpose' column since Claude already knows what jq, rg, and fd do - keep only the fallback information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant information. The architecture diagram and execution steps have overlap, and some tables (like CLI Tool Integration) explain things Claude already knows. The expert routing details section repeats information already shown in the routing table. | 2 / 3 |
Actionability | Provides concrete, executable bash commands for framework detection, file analysis, and test location conventions. The routing table with specific file patterns and expert mappings is immediately actionable, and the Task tool invocation format is clearly specified. | 3 / 3 |
Workflow Clarity | The 6-step architecture diagram provides clear sequencing with explicit steps. Each step has concrete actions, and Step 6 includes integration with TaskCreate for verification. The workflow handles multiple paths (file vs directory, different frameworks) with clear decision points. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from architecture overview to detailed steps. References to external files (frameworks.md, visual-testing.md) are one level deep and clearly signaled. The Integration section at the end appropriately links to related commands. | 3 / 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.
- 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.