python-testing

Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

A thorough, highly actionable pytest reference with executable examples throughout, but it overflows into monolithic verbosity and explains basic concepts Claude already knows. Splitting advanced material into bundled reference files and trimming redundant basics would meaningfully improve token efficiency and progressive disclosure.

Suggestions

Move large reference blocks (e.g. full marker/conftest registration, coverage configuration, hypothesis examples) into references/ files and link to them one level deep to improve progressive disclosure.

Trim explanatory prose that restates knowledge Claude already has (basic assertion forms, test discovery conventions, Arrange-Act-Act) and keep only the non-obvious pytest-specific guidance.

Add explicit validation/feedback steps for risky or batch operations such as coverage thresholds (e.g. '--cov-fail-under behavior on failure') and parallel/failed-test runs to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	Code examples are executable and well-organized, but the ~490-line body spends many tokens on basic concepts Claude already knows (e.g. 'pytest automatically discovers tests following these conventions', Basic Assertions, Arrange-Act-Act basics) and restates standard library usage; it could be tightened considerably.	2 / 3
Actionability	Provides concrete, copy-paste-ready executable code across fixtures, parametrization, mocking, coverage, async testing, and run commands, with specific flags and inline examples rather than vague direction.	3 / 3
Workflow Clarity	Content is organized by topic with clear sections, but it is a reference catalog rather than a sequenced workflow; destructive/batch-relevant operations (coverage fail-under, parallel runs, skip/skipif) lack validation checkpoints and feedback loops, capping the score at 2.	2 / 3
Progressive Disclosure	Single monolithic SKILL.md with no bundle files in references/, scripts/, or assets/; everything is inline with no one-level-deep pointers to split out advanced or large reference material (e.g. the markers/conftest/coverage detail), so structure is present but not appropriately split.	2 / 3
	Total	9 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete pytest capabilities and includes an explicit 'Use when' trigger, covering both what and when. It could be improved by adding more natural user-side trigger phrasings beyond the single 'writing or improving Python tests' clause.

Suggestions

Broaden trigger terms to natural user phrasings, e.g. 'Use when writing or improving Python tests, debugging flaky tests, adding integration tests, or increasing test coverage.'

Consider mentioning 'unittest migration to pytest' or 'test organization' as explicit triggers users are likely to voice.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions/areas: 'fixtures, parametrization, mocking, coverage analysis, async testing, and test organization' — a comprehensive enumeration of specific pytest capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers what ('Python testing best practices using pytest including...') and when ('Use when writing or improving Python tests'), satisfying the explicit 'Use when...' trigger clause required for a 3.	3 / 3
Trigger Term Quality	'Python tests', 'pytest', 'fixtures', 'parametrization', 'mocking' are relevant, but natural user phrasings like 'write tests', 'improve test coverage', 'flaky tests', or 'integration tests' are only weakly present, and 'pytest' is the dominant keyword with common variations missing.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to Python/pytest testing with distinct triggers; unlikely to fire for unrelated skills given the explicit Python + pytest + testing framing.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 4130457

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.