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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill unittest-test-creator33
Quality
3%
Does it follow best practices?
Impact
84%
0.92xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/unittest-test-creator/SKILL.mdDiscovery
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The duplicated trigger term suggests a template that wasn't properly filled out.
Suggestions
Add specific concrete actions like 'Generates unittest test classes, creates test methods with assertions, mocks dependencies, and structures test suites for Python code'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks to write unit tests, create test cases, add test coverage, or mentions unittest, pytest, or testing Python code'
Remove the duplicated trigger term and expand to include variations users naturally say: 'unit tests', 'test cases', 'write tests for', 'add tests', 'test coverage'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Unittest Test Creator' and 'Test Automation' without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating tests, generating test cases, writing assertions, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and completely lacks a 'Use when...' clause or any explicit trigger guidance. Both the what and when are missing or extremely weak. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are redundant ('unittest test creator, unittest test creator' - duplicated). Missing natural variations users would say like 'unit tests', 'test cases', 'write tests', 'testing', 'pytest', or 'test coverage'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'unittest' is somewhat specific to Python's unittest framework, 'Test Automation' is generic and could overlap with other testing skills. The lack of specific capabilities makes it harder to distinguish from other test-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 essentially a placeholder template with no actual instructional content. It describes capabilities in abstract terms without providing any concrete guidance, code examples, or workflows for creating unittest tests. The content fails all dimensions by being verbose yet empty of actionable information.
Suggestions
Add executable Python unittest code examples showing test class structure, assertions, and common patterns (e.g., setUp/tearDown, mocking with unittest.mock)
Include a clear workflow for creating tests: 1) Identify function to test, 2) Write test cases, 3) Run tests, 4) Validate coverage
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific unittest patterns and anti-patterns
Add concrete examples of test triggers with expected test output, such as 'Given this function, generate these test cases'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The entire skill describes what it does abstractly without showing how to actually create unittest tests. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic descriptions with no references to detailed materials, examples, or supporting documentation. No structure for discovery. | 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 | |
- 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.