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 concrete action descriptions — it says 'patterns' but doesn't specify what actions it performs (e.g., writing fixtures, configuring test suites, debugging test failures). The 'Triggers on:' format is functional but could be improved with a proper 'Use when...' clause describing user scenarios.
Suggestions
Add concrete actions before the trigger list, e.g., 'Writes pytest test cases, creates fixtures, configures conftest.py files, sets up parametrized tests, and implements mocking strategies.'
Replace 'Triggers on:' with a 'Use when...' clause that describes user scenarios, e.g., 'Use when the user needs help writing or debugging Python tests, setting up pytest configurations, or working with test fixtures and mocking.'
| 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 there's no clear 'Use when...' clause describing scenarios. | 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 | Highly distinctive — pytest is a specific tool with specific terminology. The trigger terms like 'conftest', 'pytest.raises', 'parametrize', and 'fixture' are unique to pytest and unlikely to conflict with other 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 efficient pytest reference. It provides executable code examples for all major pytest features while staying concise, and appropriately delegates advanced topics to clearly-signaled reference files. The structure progresses logically from simple to complex patterns, making it easy for Claude to find and apply the right pattern.
| 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 purposeful. | 3 / 3 |
Actionability | All code examples are executable and copy-paste ready. The quick reference table provides specific, runnable commands. Fixtures, parametrize, mocking, and exception testing all have complete, concrete examples. | 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 → markers → 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 one-level-deep references for advanced topics (fixtures-advanced.md, mocking-patterns.md, etc.). Scripts, assets, and related skills are well-organized and clearly navigable. | 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
f772de4
- 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.