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 essentially a label with no substantive content. It fails to describe any concrete actions the skill performs, provides no natural trigger terms beyond a repeated skill name, and lacks any explicit guidance on when Claude should select it. It would be nearly indistinguishable from other testing skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Python unittest test classes, writes test methods with assertions, creates mock objects, and scaffolds test files for existing Python modules.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to write unit tests, create test cases, generate unittest boilerplate, or add test coverage for Python code.'
Include natural keyword variations users would say: 'unit test', 'test cases', 'test coverage', 'write tests', 'Python testing', 'unittest', 'test file', 'assert'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('unittest test creator', 'Test Automation') but provides no concrete actions. It does not describe what the skill actually does—no mention of generating test cases, writing assertions, mocking, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond a label, and has no explicit 'when should Claude use it' clause. The 'Triggers on' line is just a repeated label, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'unittest test creator' repeated twice. It misses natural variations users would say like 'unit test', 'write tests', 'test cases', 'pytest', 'testing', or 'create unit tests'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'unittest' provides some specificity to Python's unittest framework, which gives it a slight niche. However, the vague 'Test Automation' category and lack of concrete details 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 an empty shell with no substantive content. It consists entirely of meta-descriptions and placeholder text that describe what the skill could do without providing any actual instructions, code examples, or concrete guidance for creating unittest tests. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to create unittest tests (e.g., a complete Python unittest.TestCase class with setUp, test methods, and assertions).
Include a clear step-by-step workflow for creating tests: identify function to test → write test class → add test methods → run tests → validate coverage.
Replace the abstract 'Capabilities' and 'Example Triggers' sections with actual guidance on mocking (unittest.mock), test fixtures, parameterized tests, and common patterns.
Add references to separate files for advanced topics like integration testing setup, pytest configuration, or TDD workflows if those are in scope.
| 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 instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code examples, no commands, no concrete steps for creating unittest tests. The 'capabilities' section describes what it could do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill merely states it 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured navigation, and no meaningful content organization beyond boilerplate headings. | 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
3076d78
- 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.