python-pytest-patterns
pytest testing patterns for Python. Triggers on: pytest, fixture, mark, parametrize, mock, conftest, test coverage, unit test, integration test, pytest.raises.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill python-pytest-patterns83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excels at trigger term coverage and distinctiveness, making it easy for Claude to identify when pytest-related help is needed. However, it lacks specificity about what concrete actions or patterns the skill teaches - it tells Claude when to use it but not what it actually does.
Suggestions
Add specific capabilities like 'Write fixtures, create parametrized tests, configure conftest.py, mock dependencies, and handle test exceptions'
Restructure to lead with concrete actions: 'Creates pytest fixtures, parametrized tests, and mock configurations. Triggers on: pytest, fixture, mark...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (pytest testing) and mentions 'patterns' but doesn't list concrete actions like 'write fixtures', 'create parametrized tests', or 'configure conftest files'. The description focuses on trigger terms rather than capabilities. | 2 / 3 |
Completeness | The 'when' is well-addressed via 'Triggers on:' with explicit keywords, but the 'what' is weak - 'pytest testing patterns' doesn't explain what actions or capabilities the skill provides. Missing explicit 'Use when...' clause but has equivalent trigger guidance. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'pytest', 'fixture', 'mark', 'parametrize', 'mock', 'conftest', 'test coverage', 'unit test', 'integration test', 'pytest.raises'. These are all terms developers naturally use when working with pytest. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with pytest-specific terminology like 'conftest', 'parametrize', 'pytest.raises', and 'fixture'. Unlikely to conflict with general Python skills or other testing frameworks due to the specific pytest vocabulary. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%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 pytest reference skill that efficiently covers core testing patterns with executable examples. The progressive disclosure is excellent, with clear navigation to advanced topics. The main weakness is the lack of an explicit testing workflow or validation guidance, though this is less critical for a reference-style skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting patterns through executable code examples without explaining basic concepts Claude already knows. Every section delivers actionable patterns without padding. | 3 / 3 |
Actionability | All code examples are complete and executable, from basic tests to fixtures, parametrize, mocking, and conftest patterns. The quick reference table provides copy-paste ready commands. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for test development or validation steps. For a reference skill covering multiple patterns rather than a multi-step process, this is acceptable but could benefit from a 'typical test workflow' section. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview of core patterns in the main file, clearly signaled one-level-deep references to advanced topics (fixtures-advanced.md, mocking-patterns.md, etc.), and well-organized sections for scripts and assets. | 3 / 3 |
Total | 11 / 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 | |
- 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.