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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-unit-tests60
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
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (unit test generation with multiple framework support), includes natural trigger terms users would actually say, explicitly states when to use it, and carves out a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'generate comprehensive unit tests', 'test cases', 'test suites', supports multiple frameworks (Jest, pytest, JUnit), and includes intelligent framework detection. Uses proper third person voice. | 3 / 3 |
Completeness | Clearly answers both what (generate unit tests from source code with framework support) AND when with explicit triggers ('Use this skill when the user asks to "generate tests", "create unit tests", or uses the shortcut "gut"'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'unit tests', 'test cases', 'test suites', 'generate tests', 'create unit tests', plus the shortcut 'gut'. Also mentions 'files' and 'code snippets' as targets. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on unit test generation with distinct triggers like 'gut' shortcut and specific framework names. Unlikely to conflict with general coding skills or other testing-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%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 marketing documentation rather than actionable instructions for Claude. It explains what the skill does conceptually but provides no concrete code examples, no actual test templates, no framework-specific syntax, and no executable guidance. Claude already knows how to write unit tests; this skill should provide project-specific conventions, preferred patterns, or concrete templates.
Suggestions
Replace abstract descriptions with concrete, executable test templates for each supported framework (Jest, pytest, JUnit) showing actual test syntax and assertions
Remove explanatory content about what unit tests are and why they matter - Claude already knows this
Add specific examples showing input source code and the exact generated test output, not just descriptions of what would happen
Include concrete commands or code patterns for mocking dependencies in each framework rather than just mentioning that mocks will be created
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what unit tests are, what mocking is, what CI/CD pipelines do). Phrases like 'empowers Claude to rapidly create robust unit tests' and 'saving developers time' are marketing fluff that waste tokens. | 1 / 3 |
Actionability | No executable code, no concrete commands, no actual test examples. The 'Examples' section describes what the skill will do abstractly rather than showing actual generated test code or specific implementation details. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists steps in sequence, but they are abstract descriptions rather than actionable instructions. No validation checkpoints, no error handling guidance, no concrete workflow Claude can follow. | 2 / 3 |
Progressive Disclosure | Content is organized into sections, but everything is in one file with no references to external documentation. The content that exists could be much more concise, and there's no clear separation between quick-start and advanced usage. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.