testgen
Generate tests with expert routing, framework detection, and auto-TaskCreate. Triggers on: generate tests, write tests, testgen, create test file, add test coverage.
73
62%
Does it follow best practices?
Impact
87%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/testgen/SKILL.mdQuality
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.
The description is strong on completeness and trigger terms, explicitly listing when it should be activated with natural user phrases. Its main weakness is that the capability descriptions ('expert routing', 'framework detection', 'auto-TaskCreate') are somewhat jargon-heavy and don't clearly convey concrete actions to the user. Overall it's a functional description that would work well for skill selection.
Suggestions
Replace internal jargon like 'expert routing' and 'auto-TaskCreate' with concrete user-facing actions, e.g., 'Generates unit and integration tests, detects testing frameworks automatically, and creates test files for existing code.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (test generation) and mentions some capabilities like 'expert routing', 'framework detection', and 'auto-TaskCreate', but these are somewhat jargon-heavy and don't clearly describe concrete user-facing actions like 'generates unit tests for functions' or 'creates integration test files'. | 2 / 3 |
Completeness | Answers both 'what' (generate tests with expert routing, framework detection, auto-TaskCreate) and 'when' (explicit 'Triggers on:' clause with specific trigger phrases), satisfying the requirement for explicit trigger guidance. | 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 realistic phrases a user would type when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to test generation with distinct trigger terms. The specificity of 'testgen', 'create test file', and 'add test coverage' makes it unlikely to conflict with other skills like general code generation or code review. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill attempts to be comprehensive but suffers from significant verbosity—it explains routing tables, framework detection, and language-specific patterns that Claude already knows, while paradoxically lacking concrete test generation examples (the core purpose). The workflow is well-sequenced but missing validation checkpoints for generated tests. Referenced bundle files (frameworks.md, visual-testing.md) don't exist, undermining the progressive disclosure strategy.
Suggestions
Drastically reduce content by removing language-specific expert routing details and CLI tool tables that Claude already knows—focus on the unique workflow logic and project convention detection that Claude wouldn't know by default.
Add concrete, executable test generation examples in Step 5 showing actual output for at least 2 languages (e.g., a TypeScript jest test and a Python pytest test), since this is the core purpose of the skill.
Add an explicit validation checkpoint between Step 5 and Step 6: run the generated tests, verify they pass, and fix any failures before suggesting next steps.
Either provide the referenced bundle files (frameworks.md, visual-testing.md) or inline the most critical examples and remove the broken references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It includes extensive routing tables, framework detection details, and expert routing descriptions that Claude could infer or that add minimal value. The ASCII architecture diagram, while visually appealing, duplicates information explained in the execution steps. Much of the content (e.g., explaining what table-driven tests are in Go, listing every file extension mapping) is knowledge Claude already possesses. | 1 / 3 |
Actionability | The skill provides concrete bash commands for framework detection and target analysis, which is good. However, the core test generation step (Step 5) is entirely abstract—it lists categories and depth levels in tables but provides zero executable test code examples. The 'Route to Expert Agent' step references a 'Task tool' invocation with pseudocode-like structure rather than actual executable commands. The most critical step (actually generating tests) lacks any concrete code. | 2 / 3 |
Workflow Clarity | The 6-step sequence is clearly laid out and logically ordered. However, there are no validation checkpoints—no step verifies that generated tests actually compile or pass before suggesting next steps. For a test generation workflow that creates files, there should be an explicit 'run tests and verify they pass' validation step before the integration step, not just a suggestion afterward. | 2 / 3 |
Progressive Disclosure | The skill references `frameworks.md` and `visual-testing.md` for detailed examples, which is good progressive disclosure. However, no bundle files are provided, so these references are broken. The main SKILL.md itself contains too much inline detail (expert routing details, CLI tool tables, full test location conventions) that should be in separate reference files, making the overview too long. | 2 / 3 |
Total | 7 / 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
- NeverSight/skills_feed
- Commit
3ae408c
- 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.