python-pytest-patterns
pytest testing patterns for Python. Triggers on: pytest, fixture, mark, parametrize, mock, conftest, test coverage, unit test, integration test, pytest.raises.
76
74%
Does it follow best practices?
Impact
68%
0.95xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/python-pytest-patterns/SKILL.mdQuality
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has strong trigger term coverage and clear distinctiveness for pytest-related tasks, but falls short on specificity of capabilities — it says 'patterns' without listing what concrete actions it enables (e.g., writing fixtures, configuring test suites, debugging test failures). The 'Triggers on:' clause effectively communicates when to use the skill, but the what-it-does portion is underdeveloped.
Suggestions
Replace 'pytest testing patterns for Python' with specific actions like 'Write and organize pytest test suites, create fixtures, parametrize tests, configure conftest files, and set up mocking for Python projects.'
Add a 'Use when...' clause that complements the trigger terms, e.g., 'Use when the user needs help writing, debugging, or structuring Python tests using pytest.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (pytest testing) and implies actions through trigger terms like 'fixture', 'parametrize', 'mock', but doesn't list concrete actions (e.g., 'write test fixtures', 'configure conftest files', 'set up parametrized tests'). It describes patterns rather than specific capabilities. | 2 / 3 |
Completeness | The 'what' is partially addressed ('pytest testing patterns for Python') but lacks specific actions. The 'when' is addressed via 'Triggers on:' which serves as an explicit trigger clause, but the what-it-does portion is too thin. The trigger list partially compensates but the description doesn't clearly explain what the skill actually does beyond 'patterns'. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'pytest', 'fixture', 'parametrize', 'mock', 'conftest', 'test coverage', 'unit test', 'integration test', 'pytest.raises'. These are all terms a developer would naturally use when seeking help with pytest. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to pytest in Python with very specific trigger terms like 'conftest', 'pytest.raises', 'parametrize', and 'fixture'. This is unlikely to conflict with other skills unless there's another Python testing skill. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid pytest patterns skill with excellent actionability — every section contains real, executable code examples covering the key pytest features. The progressive disclosure structure is well-designed with clear references to advanced topics, but the absence of actual bundle files undermines those references. Conciseness could be improved by trimming basic patterns Claude already knows (like simple assertions) and tightening some explanatory comments.
Suggestions
Remove the 'Basic Test Structure' section or reduce it to a single example — Claude already knows how to write basic assertions and doesn't need `assert 1 + 1 == 2`.
Provide the referenced bundle files (fixtures-advanced.md, mocking-patterns.md, etc.) to fulfill the progressive disclosure promises made in the skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary elements like basic test structure (assert 1+1==2) and docstring patterns that Claude already knows. The fixture scope comments and some inline explanations could be trimmed. | 2 / 3 |
Actionability | All code examples are concrete, executable, and copy-paste ready. The quick reference table provides specific commands with clear descriptions. Patterns cover fixtures, parametrize, mocking, markers, and conftest with real working code. | 3 / 3 |
Workflow Clarity | For a reference/patterns skill (not a multi-step destructive workflow), the content is well-sequenced from basic tests through fixtures, parametrize, exceptions, markers, mocking, and conftest. The quick reference table provides clear command sequences. No destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | The skill has excellent structure with clear references to 7 detailed reference files, scripts, and assets. However, no bundle files were provided, meaning all those references point to non-existent files. The main SKILL.md itself is well-organized but includes substantial inline content that could arguably be in references. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
2d09b29
- 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.