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

58%

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

46%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 content is highly actionable with abundant executable examples but suffers from verbosity and a monolithic structure that explains concepts and patterns Claude already knows. Splitting topics into reference files and trimming boilerplate examples would materially improve it.

Suggestions

Move exhaustive reference material (markers, coverage config, property-based testing) into separate files under references/ and keep SKILL.md as a concise overview with links.

Trim sections that re-explain basics Claude already knows (test discovery conventions, basic assert forms, simple Mock usage) to reduce token cost.

Add a sequenced workflow with validation checkpoints for risky tasks such as reaching a coverage threshold or diagnosing a flaky test.

Dimension	Reasoning	Score
Conciseness	The body extensively demonstrates pytest patterns Claude already knows (basic asserts, discovery conventions, simple Mock usage) across ~480 lines, padding the context with examples that earn few new tokens.	2 / 5
Actionability	It provides numerous copy-paste-ready, executable code snippets and bash commands covering common pytest cases, with only minor gaps (e.g. setup/install steps assumed).	4 / 5
Workflow Clarity	Sections are well-organized by topic but there is no sequenced multi-step process with validation checkpoints for risky operations like running coverage gates or debugging flaky tests.	3 / 5
Progressive Disclosure	Despite being long, the skill is a monolithic single-file reference with no bundle files and no navigation to deeper materials; topic-specific detail that belongs in separate references is all inlined.	2 / 5
	Total	11 / 20 Passed

Description

71%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 well-targeted to pytest-based Python testing with a clear use-when clause, giving it strong distinctiveness and specificity. Trigger-term coverage and the explicitness of the 'when' guidance are the main areas for improvement.

Suggestions

Add common user trigger phrases to the description such as 'unit tests', 'test coverage', 'flaky tests', or 'test fixtures' to improve natural keyword coverage.

Expand the 'Use when' clause with concrete triggers, e.g. 'Use when writing, debugging, or improving Python tests, or setting up pytest infrastructure'.

Dimension	Reasoning	Score
Specificity	Names the domain (pytest) and several concrete capability areas (fixtures, parametrization, mocking, coverage, async testing, test organization), which lists several specific actions with only minor coverage gaps.	4 / 5
Completeness	It clearly states what it does (Python testing best practices using pytest including...) and includes a 'Use when writing or improving Python tests' clause, though the when could list more specific triggers.	4 / 5
Trigger Term Quality	It includes 'pytest', 'Python tests', and 'writing or improving tests', but lacks natural synonym variations like 'unit tests', 'test coverage', or 'flaky tests' that users commonly say.	3 / 5
Distinctiveness Conflict Risk	The pytest-specific scope plus globs for .py files and the explicit testing focus carve a clear niche with minimal conflict risk against non-testing skills.	5 / 5
	Total	16 / 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
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
Path: .kiro/skills/python-testing/SKILL.md
Commit: ca185ef

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.