pytest-test-generator
Pytest Test Generator - Auto-activating skill for Test Automation. Triggers on: pytest test generator, pytest test generator Part of the Test Automation skill category.
34
Quality
3%
Does it follow best practices?
Impact
90%
1.00xAverage 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/pytest-test-generator/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 severely underdeveloped, functioning more as a label than a useful skill description. It lacks concrete actions, natural trigger terms, and explicit guidance on when to use it. The redundant trigger term and reliance on category labeling provide minimal value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates pytest test functions, creates fixtures, writes parameterized tests, and adds assertions for Python code'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks to write tests, create unit tests, generate pytest cases, or add test coverage to Python code'
Add natural keyword variations users would say: 'unit tests', 'test cases', 'testing Python', 'write tests for', 'test coverage', '.py tests'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Pytest Test Generator') and category ('Test Automation') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of generating tests, analyzing code, creating fixtures, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('pytest test generator' listed twice) and overly specific. Missing natural variations users would say like 'write tests', 'unit tests', 'test cases', 'testing', or 'create pytest'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'pytest' specifically provides some distinctiveness from general testing skills, but the lack of specific capabilities means it could still conflict with other test-related skills. The category label 'Test Automation' is generic. | 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 what a pytest test generator skill would do without providing any concrete guidance, code examples, or workflows. The content fails all dimensions by being verbose yet empty of actionable information.
Suggestions
Add executable pytest code examples showing how to generate tests (e.g., fixture patterns, parametrized tests, mocking examples)
Define a clear workflow: analyze code -> identify test cases -> generate test structure -> add assertions -> validate coverage
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific pytest patterns and commands
Include concrete examples of input code and expected test output to make the skill actionable
| 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 generate pytest 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 vague 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 | |
- Commit
60433a6
- 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.