jbvc/python-testing-patterns
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
61
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates both what the skill does and when to use it, with good trigger term coverage for Python testing scenarios. Its main weaknesses are slightly vague capability language ('comprehensive testing strategies') and some potential overlap risk with other testing-related skills. The explicit 'Use when...' clause and specific tool mentions (pytest, fixtures, mocking) are strong points.
Suggestions
Replace 'comprehensive testing strategies' with more concrete actions like 'Write unit tests, create pytest fixtures, mock dependencies, configure test suites'
Add file extension triggers like '.py test files' or 'test_*.py' to further reduce conflict risk with non-Python testing skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (testing) and some actions/tools (pytest, fixtures, mocking, TDD), but doesn't list multiple concrete discrete actions like 'write unit tests, create fixtures, mock dependencies, generate test reports'. The phrase 'comprehensive testing strategies' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement testing strategies with pytest, fixtures, mocking, TDD) and 'when' (explicit 'Use when writing Python tests, setting up test suites, or implementing testing best practices'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'pytest', 'fixtures', 'mocking', 'test-driven development', 'Python tests', 'test suites', 'testing best practices'. These cover common variations of how users would describe testing needs. | 3 / 3 |
Distinctiveness Conflict Risk | While pytest and Python-specific testing is fairly distinct, the broad phrase 'testing best practices' could overlap with testing skills for other languages or frameworks. It's reasonably specific to Python/pytest but could conflict with general testing or quality assurance skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a hollow shell that defers all substantive content to an external file while providing no actionable guidance, no code examples, and no concrete testing patterns in the main body. The instructions are generic boilerplate that could apply to any domain and teach Claude nothing about Python testing. The skill fails its core purpose of providing executable, specific guidance for pytest-based testing.
Suggestions
Add at least 2-3 concrete, executable pytest code examples directly in SKILL.md covering common patterns (basic test, fixture usage, mocking with unittest.mock/pytest-mock)
Replace the generic instruction bullets with specific pytest workflows, e.g., 'Run tests with `pytest -v --tb=short`, use `@pytest.fixture` for setup/teardown, mock external calls with `monkeypatch` or `unittest.mock.patch`'
Add a quick-start section showing a minimal test file structure and how to run it, so the skill provides immediate value without requiring the external resource
Remove the generic 'Do not use this skill when' section and the vague instruction bullets ('Clarify goals, constraints') that waste tokens without adding testing-specific knowledge
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Use this skill when' and 'Do not use this skill when' sections are somewhat padded and don't add actionable value. The instructions section is generic filler that Claude already knows ('Clarify goals, constraints, and required inputs'). However, it's not excessively verbose overall. | 2 / 3 |
Actionability | There is no concrete code, no executable examples, no specific commands, and no pytest-specific guidance. The instructions are entirely generic platitudes like 'Apply relevant best practices and validate outcomes' that could apply to any skill. No actual testing patterns are taught. | 1 / 3 |
Workflow Clarity | There is no clear workflow, no sequenced steps for writing tests or setting up test infrastructure, and no validation checkpoints. The four bullet points in Instructions are vague directives with no testing-specific process. | 1 / 3 |
Progressive Disclosure | There is a reference to `resources/implementation-playbook.md` which is one level deep and clearly signaled. However, the SKILL.md itself contains essentially zero useful overview content — it's just a pointer to another file with no quick-start or summary of key patterns, making the top-level document nearly empty of substance. | 2 / 3 |
Total | 6 / 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.
Reviewed
Table of Contents