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

66%

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 ./.kiro/skills/python-testing/SKILL.md

Quality

Content

50%

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

A highly actionable pytest reference packed with executable examples, but it is over-long and verbose for material Claude largely already knows, and it is a monolithic single file with no progressive disclosure or explicit validation feedback loops.

Suggestions

Cut the basic tutorial sections (basic assertions, basic test structure, basic fixtures) that Claude already knows; retain only project-specific conventions (80% coverage target, TDD cycle, marker setup, directory layout, pytest.ini config).

Add explicit validation/feedback loops to the workflow, e.g. 'run pytest --cov; if coverage < 80% add tests for uncovered lines; re-run until green'.

Move advanced material (mocking patterns, async testing, API/DB test patterns) into separate reference files (e.g., MOCKING.md, ADVANCED.md) and keep SKILL.md as a concise overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The ~815-line body is a full pytest tutorial explaining basics Claude already knows—"Equality / Inequality / Truthiness / Membership" assertions, basic test structure, basic fixtures—padded with unnecessary context, matching the verbose 'explains concepts Claude knows' anchor.	1 / 3
Actionability	It provides abundant executable, copy-paste-ready code and commands (fixtures, @pytest.mark.parametrize, @patch, pytest.ini, pyproject.toml, bash run commands), matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	The TDD red-green-refactor cycle gives a numbered sequence, but there are no explicit validation checkpoints or feedback loops (e.g., run coverage, check ≥80%, add tests, re-run), so checkpoints are only implicit.	2 / 3
Progressive Disclosure	Section headers provide structure, but the skill is a monolithic single file (~815 lines) with no external references, so content that should be split out (advanced mocking, async, API/DB patterns) is inline rather than progressively disclosed.	2 / 3
	Total	8 / 12 Passed

Description

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.

A specific, keyword-rich description that names the right techniques and occupies a distinct niche, but it omits an explicit 'Use when...' trigger clause so it answers 'what' but not 'when'.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when writing Python tests, setting up pytest, or applying TDD', to raise completeness and surface natural trigger phrasing.

Reframe the technique list into concrete actions (e.g., 'Write and run pytest tests, apply TDD red-green-refactor, build fixtures and mocks, parametrize cases, and enforce 80% coverage') to sharpen specificity and trigger term quality.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete techniques—"pytest、TDD手法、フィクスチャ、モック、パラメータ化、カバレッジ要件"—rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly states what the skill does ("Pythonテスト戦略" built on the listed techniques) but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric it caps at 2.	2 / 3
Trigger Term Quality	It includes natural terms a user would actually say (pytest, TDD, フィクスチャ, モック, カバレッジ, パラメータ化), giving good coverage of the domain's natural vocabulary.	3 / 3
Distinctiveness Conflict Risk	The pytest + TDD + Python testing framing carves a clear niche unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 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
skill_md_line_count	SKILL.md is long (816 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/python-testing/SKILL.md
Commit: 0c1d7be

Reviewed: 3 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.