CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

84

Quality

81%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

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 strong, technically detailed description that excels at specificity and trigger term coverage for pytest-related queries. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over other testing or Python-related skills.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about pytest setup, writing tests, test fixtures, mocking in tests, or test coverage configuration.'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and features: 'Set up pytest 8.x', 'unit and integration testing', 'fixtures (scope, autouse, parametrize)', 'async tests', 'mocking', 'coverage', 'conftest.py patterns', and 'markers'.

3 / 3

Completeness

Clearly answers 'what does this do' with comprehensive feature list, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill.

2 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'pytest', 'unit testing', 'integration testing', 'fixtures', 'async tests', 'mocking', 'coverage', 'conftest.py', 'markers', 'pytest-asyncio', 'pytest-mock', 'pytest-cov'.

3 / 3

Distinctiveness Conflict Risk

Very specific niche targeting pytest 8.x with Python, including specific plugins and patterns. Unlikely to conflict with other testing frameworks or general Python skills due to explicit pytest focus.

3 / 3

Total

11

/

12

Passed

Implementation

79%

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, actionable pytest skill with excellent code examples covering fixtures, async testing, mocking, and parametrization. The content is appropriately concise and assumes Claude's competence. Main weaknesses are the lack of explicit validation steps in multi-step workflows (especially database setup) and the monolithic structure that could benefit from progressive disclosure to separate files.

Suggestions

Add explicit validation steps for database setup workflow (e.g., 'Verify container is ready: `docker compose -f docker-compose.test.yml ps` should show healthy status before running `pytest -m integration`')

Split advanced topics (Factory Boy, external HTTP mocking, Docker test database setup) into separate reference files and link from a 'See also' section

Add a verification step after running coverage to check threshold (e.g., 'Verify coverage meets minimum: check that `--cov-fail-under=80` passes')

DimensionReasoningScore

Conciseness

The skill is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary explanations about what pytest is or how testing works.

3 / 3

Actionability

Fully executable code throughout - from installation commands to complete test examples, fixture patterns, and CLI commands. All examples are copy-paste ready with realistic use cases including async tests, mocking, and database integration.

3 / 3

Workflow Clarity

While individual patterns are clear, the skill lacks explicit validation checkpoints for multi-step processes like setting up test databases or running integration tests. The Docker setup mentions starting the container but doesn't include verification that it's ready before running tests.

2 / 3

Progressive Disclosure

Content is well-organized with clear sections, but it's a monolithic document (~300 lines) that could benefit from splitting advanced topics (Factory Boy, external API mocking, Docker setup) into separate reference files. The Integration Notes section hints at external skills but doesn't provide clear navigation structure.

2 / 3

Total

10

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
achreftlili/deep-dev-skills
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.