python-testing

Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements. Use when writing pytest tests — fixtures, mocks, parametrization, or coverage.

Quality

87%

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

Quality

Content

86%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.

A dense, code-first reference that is lean and highly actionable, with executable examples across the full pytest feature set. Its weaknesses are structural: the monolithic single-file layout offers no progressive disclosure, and the test-authoring workflow lacks explicit validation feedback loops.

Suggestions

Split the bulk reference material into one-level-deep files (e.g. references/fixtures.md, references/mocking.md, references/async.md) and link to them from SKILL.md so the overview stays lean and navigable.

Add an explicit test-authoring workflow with validation checkpoints — e.g. 'write failing test → run pytest → confirm RED → implement → run until GREEN → check coverage with pytest --cov → refactor → re-run'.

Trim the duplicated config-file examples (pytest.ini and pyproject.toml cover the same markers/addopts); keep one inline and reference the other to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code blocks with terse headers and one-line descriptions — no padded prose explaining pytest, Python, or TDD concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Copy-paste-ready, fully executable examples cover the common cases thoroughly — fixtures, parametrization, mocking, async, exceptions, tmp_path, API/database testing, config files, and run commands.	5 / 5
Workflow Clarity	The TDD cycle (RED/GREEN/REFACTOR) and the running-tests command catalog are clearly sequenced, but there are no explicit validate→fix→retry feedback loops or checklists for the test-authoring process.	4 / 5
Progressive Disclosure	Section headers give good structure, but the ~810-line body is monolithic — all content (mocking, async, config-file variants) is inlined in SKILL.md with no references to separate files, and no bundle files exist to split the load.	3 / 5
	Total	17 / 20 Passed

Description

88%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.

A strong, third-person description that pairs a comprehensive capability list with an explicit 'Use when' trigger clause. Trigger term coverage is good but lacks synonyms and extensions, and a couple of broad phrases ('TDD methodology', 'testing strategies') carry minor overlap risk with adjacent skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements' — giving comprehensive coverage of the skill's surface rather than a few actions with gaps.	5 / 5
Completeness	Explicitly answers 'what' ('Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements') and 'when' ('Use when writing pytest tests — fixtures, mocks, parametrization, or coverage') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms users say are present — 'pytest tests', 'fixtures', 'mocks', 'parametrization', 'coverage' — but synonyms and file/extension variants (e.g. 'unit tests', 'test coverage', '.py') are missing.	4 / 5
Distinctiveness Conflict Risk	The pytest-specific triggers (fixtures, mocks, parametrization, coverage) carve a clear niche, but 'TDD methodology' and 'testing strategies' could overlap with a more general testing or Python skill.	4 / 5
	Total	18 / 20 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
skill_md_line_count	SKILL.md is long (818 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/python-testing/SKILL.md
Commit: e04ea0b

Reviewed: 2 days 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.