unittest-test-creator
Unittest Test Creator - Auto-activating skill for Test Automation. Triggers on: unittest test creator, unittest test creator Part of the Test Automation skill category.
33
3%
Does it follow best practices?
Impact
84%
0.92xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/unittest-test-creator/SKILL.mdQuality
Discovery
7%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 description is extremely weak across all dimensions. It reads like an auto-generated stub with no meaningful content—just repeating the skill name as both the description and trigger terms. It provides no concrete actions, no natural trigger keywords users would use, and no explicit guidance on when Claude should select this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Python unittest test classes, creates test methods with assertions, mocks dependencies, and structures test files following unittest conventions.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to write unit tests, create test cases, generate test files, add test coverage, or mentions Python unittest, test classes, or test methods.'
Diversify trigger terms to include natural variations users would say: 'unit test', 'write tests', 'test cases', 'test coverage', 'testing', 'create tests for', 'add tests', 'pytest', '.py test file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('unittest test creator') but does not describe any concrete actions. There are no specific capabilities listed like 'generates unit test files', 'creates test cases for functions', or 'mocks dependencies'. | 1 / 3 |
Completeness | The 'what' is extremely vague (just the name 'Unittest Test Creator') and the 'when' is essentially absent—'Triggers on: unittest test creator' is a duplicate label, not meaningful trigger guidance. Neither question is adequately answered. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'unittest test creator' repeated twice. Missing natural variations users would say like 'unit test', 'write tests', 'test cases', 'pytest', 'testing', 'test coverage', or 'create tests'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'unittest' specifically (Python's unittest framework) provides some distinctiveness from general testing skills, but the lack of specificity about what it actually does and the broad 'Test Automation' category could cause overlap with other testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual instructional content. It repeatedly references 'unittest test creator' without ever defining what that means, providing code examples, explaining patterns, or giving any actionable guidance. It fails on every dimension because it contains no substance—only meta-descriptions of what a skill would theoretically do.
Suggestions
Replace the abstract descriptions with concrete, executable code examples showing how to create unittest tests (e.g., a complete Python unittest.TestCase class with setUp, test methods, and assertions).
Add a clear workflow section with specific steps: create test file, write test class, run tests, interpret output, with validation checkpoints like 'run `python -m pytest --tb=short` and verify all tests pass'.
Include specific patterns for common testing scenarios: mocking with unittest.mock, parameterized tests, fixture setup/teardown, and integration test patterns with concrete code.
Remove all meta-content about 'when to use' and 'example triggers'—these waste tokens on information that doesn't help Claude actually write tests.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'unittest test creator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no specific patterns, no frameworks configuration. The content only describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions of any kind. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no layered organization, and the sections are superficial headers over vacuous content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.