python-pytest-patterns
pytest testing patterns for Python. Triggers on: pytest, fixture, mark, parametrize, mock, conftest, test coverage, unit test, integration test, pytest.raises.
84
86%
Does it follow best practices?
Impact
68%
0.95xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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, making it easy to select from a pool of skills. However, it lacks explicit concrete actions (what the skill actually does beyond 'patterns') and would benefit from a proper 'Use when...' clause to improve completeness.
Suggestions
Add specific concrete actions such as 'Write test functions, create fixtures, configure conftest.py, set up parametrized tests, mock dependencies, and measure test coverage.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about writing or debugging Python tests, configuring pytest, or improving test coverage.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('pytest testing patterns for Python') and lists trigger terms that hint at specific actions (fixtures, parametrize, mock, conftest), but it does not explicitly describe concrete actions like 'write fixtures', 'configure conftest files', or 'set up parametrized tests'. | 2 / 3 |
Completeness | The 'what' is weakly stated as 'pytest testing patterns for Python' without listing specific capabilities. The 'when' is partially addressed via 'Triggers on:' with a list of keywords, but there is no explicit 'Use when...' clause describing scenarios, which caps this at 2. | 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', and 'mark'. 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 specifically, with highly distinctive trigger terms like 'conftest', 'pytest.raises', 'parametrize', and 'fixture' that are unlikely to conflict with other testing or Python skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that serves as an effective pytest reference. It provides concise, executable code examples for all major pytest features while maintaining excellent organization with clear pointers to advanced reference materials. The content respects Claude's intelligence by avoiding explanations of basic concepts and focusing purely on actionable patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It jumps straight into code examples without explaining what pytest is or how testing works. Every section delivers concrete patterns without unnecessary prose. Docstrings within code are minimal and functional. | 3 / 3 |
Actionability | All code examples are executable and copy-paste ready. The quick reference table provides specific CLI commands. Fixtures, parametrize, mocking, and exception testing all have complete, runnable examples with clear patterns. | 3 / 3 |
Workflow Clarity | This is a reference/pattern skill rather than a multi-step destructive workflow, so explicit validation checkpoints aren't required. The content is clearly sequenced from basic tests → fixtures → parametrize → exceptions → mocking → conftest, which is a logical learning progression. The quick reference table provides clear command sequences. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The main file provides a concise overview of all key patterns, then clearly signals seven reference files for advanced topics, plus scripts and asset templates. All references are one level deep and well-labeled with descriptive names. | 3 / 3 |
Total | 12 / 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
9f4534c
- 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.