pytest-testing-skill

Set up pytest 8.x with Python for unit and integration testing using fixtures (scope, autouse, parametrize), async tests (pytest-asyncio), mocking (unittest.mock, pytest-mock), coverage (pytest-cov), conftest.py patterns, and markers.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./testing/pytest-testing-skill/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with comprehensive executable examples, but it is long and redundant, lacks an explicit test-run/fix/retry feedback loop, and inlines all content with no progressive disclosure to separate files.

Suggestions

Move the more advanced pattern sections (factory_boy, responses mocking, integration DB setup) into reference files and point to them from SKILL.md to improve progressive disclosure and token efficiency.

Add an explicit verification workflow with a checkpoint, e.g. 'Run pytest, fix failures, re-run with --lf until green' before treating setup as complete.

Consolidate the duplicate mocking coverage (unittest.mock, pytest-mock, responses) into one section to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code and commands with no concept padding, but at ~400 lines it has notable redundancy (two conftest.py examples, three mocking approaches) and stray comments like 'Cleanup runs after all tests complete', so it could be tightened.	3 / 5
Actionability	It provides fully executable, copy-paste-ready code and commands across all common cases — install commands, pyproject config, fixtures, unit tests, parametrize, async tests, factory_boy, markers, and common pytest commands.	5 / 5
Workflow Clarity	The content is a reference of patterns rather than a sequenced workflow, and verification lacks explicit checkpoints; running a test suite (a batch operation) has no validate-fix-retry feedback loop, so it sits at the anchor-3 level.	3 / 5
Progressive Disclosure	Section structure is clear (Prerequisites, Scaffold, Project Structure, Patterns, Commands, Integration Notes), but everything is inlined into one ~400-line SKILL.md with no bundle files or signaled references to split the bulk pattern content.	3 / 5
	Total	14 / 20 Passed

Description

75%Weight 40%Scale 1-5

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 is specific and distinctive, listing concrete pytest capabilities and natural trigger terms, but it omits any explicit 'Use when...' guidance, which caps completeness at 3. Adding a trigger clause would raise the score.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when setting up or writing Python tests with pytest, fixtures, async tests, mocking, or coverage.'

Include a few more natural user phrasings such as 'writing tests', 'test mocks', or 'test coverage' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete capabilities — 'unit and integration testing using fixtures (scope, autouse, parametrize), async tests (pytest-asyncio), mocking (unittest.mock, pytest-mock), coverage (pytest-cov), conftest.py patterns, and markers' — giving comprehensive coverage of the skill's domain.	5 / 5
Completeness	The 'what' is clearly stated ('Set up pytest 8.x with Python for unit and integration testing using...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural terms a user would say ('pytest', 'unit and integration testing', 'fixtures', 'mocking', 'coverage', 'conftest.py', 'markers') are well covered with library names, but a few common phrasings like 'writing tests' or 'mocks' are missing.	4 / 5
Distinctiveness Conflict Risk	'Set up pytest 8.x with Python for unit and integration testing' carves a clear niche tied to pytest/Python testing with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: testing/pytest-testing-skill/SKILL.md
Commit: 181fcbc

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.