testing-python
Python testing with pytest: fixtures, parametrize, mocking with unittest.mock, and coverage
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
64%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 excels at specificity and trigger term quality by naming concrete pytest features and using natural developer terminology. However, it critically lacks any 'Use when...' guidance, which means Claude has no explicit signal for when to select this skill over others. Adding trigger conditions would significantly improve its effectiveness in a multi-skill selection scenario.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about writing tests in Python, pytest fixtures, test parametrization, mocking dependencies, or measuring code coverage.'
Consider adding file extension triggers like '.py test files', 'conftest.py', or 'pytest.ini' to help Claude match on project context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: fixtures, parametrize, mocking with unittest.mock, and coverage. These are distinct, well-defined actions/concepts within the pytest ecosystem. | 3 / 3 |
Completeness | Describes 'what' (Python testing with pytest and specific features) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'pytest', 'fixtures', 'parametrize', 'mocking', 'unittest.mock', 'coverage', 'Python testing'. These are terms developers naturally use when seeking help with Python testing. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Python testing with pytest specifically, including named sub-tools (fixtures, parametrize, unittest.mock, coverage). This is a well-defined niche 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 strong, well-crafted skill that efficiently covers pytest essentials with executable examples and clear conventions. It respects Claude's intelligence by avoiding explanations of basic concepts and focuses entirely on actionable patterns. The only minor issue is the mocking example has a redundant `mock_smtp` parameter in the function signature that conflicts with the `patch` context manager, but the intent is clear.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and directly useful. No explanations of what pytest is or how testing works conceptually—just conventions, patterns, and executable examples. Every token earns its place. | 3 / 3 |
Actionability | Provides fully executable code examples for each major concept (fixtures, parametrize, mocking, basic test structure) plus concrete commands for running tests and coverage. Copy-paste ready. | 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 single-task sections are unambiguous, and the coverage section provides a clear CI integration pattern with threshold enforcement. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into clearly labeled sections that serve as a quick-reference guide. Each section is appropriately scoped and easy to navigate. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ucdavis/ai-skills-registry
- Commit
c0b2e4b
- 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.