unittest-test-creator
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill unittest-test-creatorUnittest Test Creator - Auto-activating skill for Test Automation. Triggers on: unittest test creator, unittest test creator Part of the Test Automation skill category.
Validation
69%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
0%This skill content is essentially a placeholder template with no substantive guidance. It describes what a unittest test creator skill should do without providing any actual instructions, code examples, or concrete patterns. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add executable Python unittest code examples showing basic test structure, assertions, and test discovery patterns
Include specific guidance on mocking with unittest.mock, showing concrete examples of patching and MagicMock usage
Define a clear workflow for test creation: 1) identify test cases, 2) write test class structure, 3) implement assertions, 4) run and validate
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about unittest test creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The content describes what the skill does abstractly but never shows how to actually create unittest tests - no examples, no code snippets, no specific patterns. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed materials, no links to examples or advanced topics, and no clear organization of content. | 1 / 3 |
Total | 4 / 12 Passed |
Activation
0%This description is severely underdeveloped, consisting mainly of the skill name repeated and a generic category label. It provides no concrete actions, no natural trigger terms users would actually say, and no guidance on when Claude should select this skill. The description would be nearly useless for skill selection among multiple testing-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates unittest test classes, generates test methods with assertions, sets up mock objects and fixtures for Python code'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks to write unit tests, create test cases, add test coverage, or mentions unittest, pytest, or testing Python code'
Include file type indicators and distinguishing details, e.g., 'for Python .py files using the unittest framework' to differentiate from other testing skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Test Automation') and repeats the skill name but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating test files, generating assertions, mocking, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague 'Test Automation' category, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('unittest test creator, unittest test creator'). Missing natural variations users would say like 'write unit tests', 'create test cases', 'testing', 'pytest', 'test coverage', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'Test Automation' could apply to many testing skills. Without specific capabilities or file types mentioned, it would easily conflict with other testing-related skills. | 1 / 3 |
Total | 4 / 12 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.