generating-unit-tests
This skill enables Claude to automatically generate comprehensive unit tests from source code. It is triggered when the user requests unit tests, test cases, or test suites for specific files or code snippets. The skill supports multiple testing frameworks including Jest, pytest, JUnit, and others, intelligently detecting the appropriate framework or using one specified by the user. Use this skill when the user asks to "generate tests", "create unit tests", or uses the shortcut "gut" followed by a file path.
63
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/unit-test-generator/skills/unit-test-generator/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 strong skill description that clearly communicates what the skill does (generates unit tests with multi-framework support), when to use it (explicit trigger phrases and shortcut), and occupies a distinct niche. The description is well-structured, uses third person voice appropriately, and includes natural trigger terms that users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'generate comprehensive unit tests from source code', supports 'Jest, pytest, JUnit', 'intelligently detecting the appropriate framework'. Names specific frameworks and describes the detection behavior. | 3 / 3 |
Completeness | Clearly answers both what ('generate comprehensive unit tests from source code' with framework support) and when ('Use this skill when the user asks to "generate tests", "create unit tests", or uses the shortcut "gut"'). Has an explicit 'Use this skill when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'unit tests', 'test cases', 'test suites', 'generate tests', 'create unit tests', and the shortcut 'gut'. These cover common variations of how users would phrase test generation requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to unit test generation from source code, with specific framework mentions and a unique shortcut trigger 'gut'. Unlikely to conflict with general coding skills or other testing-related skills like integration testing or test running. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a product description or README rather than actionable instructions for Claude. It explains Claude's own capabilities back to it, provides no executable code examples or templates, and lacks any concrete guidance on test structure, naming conventions, assertion patterns, or framework-specific syntax. The content would need a complete rewrite focused on concrete templates, example outputs, and specific patterns to be useful.
Suggestions
Replace the abstract 'How It Works' section with concrete code templates for each supported framework (Jest, pytest, JUnit) showing actual test file structure, imports, and assertion patterns.
Add at least one complete input/output example showing real source code and the corresponding generated test file, rather than describing what the skill 'will do' in abstract terms.
Remove the 'Overview', 'When to Use', and 'Integration' sections entirely—they explain concepts Claude already knows and waste tokens on marketing language.
Add a validation step instructing Claude to verify generated tests are syntactically correct and that imports/mocks match the actual dependencies in the source file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is highly verbose and explains concepts Claude already knows (what unit tests are, what mocking is, what edge cases are). Phrases like 'empowers Claude to rapidly create robust unit tests, saving developers time' are marketing fluff. The 'How It Works' section describes Claude's own reasoning process back to it, which is wasteful. The 'When to Use This Skill' section repeats the trigger conditions from the description. | 1 / 3 |
Actionability | There is zero executable code, no concrete test templates, no specific commands, and no actual examples of generated output. The 'Examples' section describes what the skill 'will do' in abstract terms rather than showing actual input/output pairs with real code. There is nothing copy-paste ready or directly usable. | 1 / 3 |
Workflow Clarity | The 'How It Works' steps describe abstract cognitive processes (analyze, determine, generate) rather than actionable workflow steps with concrete commands or validation checkpoints. There is no validation step to verify generated tests compile or pass, no feedback loop for fixing issues, and no concrete sequencing of file operations. | 1 / 3 |
Progressive Disclosure | The content has clear section headers and some organizational structure (Overview, How It Works, Examples, Best Practices), but it's a monolithic file with no references to external resources. The content that exists is all inline and could benefit from splitting detailed framework-specific guidance into separate files, though the skill is simple enough that this is a minor issue. | 2 / 3 |
Total | 5 / 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.
- Commit
c8a915c
- 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.