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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill pytest-test-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a title rather than a functional description. It lacks any explanation of capabilities, concrete actions, or usage triggers. The redundant trigger terms and missing 'Use when...' clause make it nearly useless for skill selection among multiple options.
Suggestions
Add specific 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 'write tests', 'unit tests', 'test my code', 'pytest', 'test cases', 'testing Python'
Remove the redundant duplicate trigger term and expand with varied natural language phrases users would actually say
| 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 completely lacks any '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 'pytest test generator' repeated twice, which is redundant and unlikely to match natural user queries. Missing common variations like 'write tests', 'unit tests', 'test cases', 'testing', or 'create pytest'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Pytest' provides some specificity that distinguishes it from generic testing skills, but 'Test Automation' is broad and could overlap with other testing-related skills. The lack of specific capabilities makes differentiation difficult. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a pytest test generator skill would do, without any concrete guidance, code examples, or workflows for actually generating pytest tests. The content fails all dimensions by being verbose yet empty of actionable information.
Suggestions
Add executable pytest code examples showing how to generate tests for common scenarios (functions, classes, fixtures)
Include a concrete workflow: 1) Analyze target code, 2) Identify test cases, 3) Generate test file with specific structure, 4) Validate tests run
Provide specific pytest patterns like parametrize, fixtures, mocking with concrete syntax examples
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual pytest-specific instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about pytest test generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The content describes what the skill does abstractly but never shows how to actually generate pytest tests. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for generating tests. | 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
69%Validation — 11 / 16 Passed
Validation for skill structure
| 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 | |
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.