CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/python-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized, code-dense pytest reference that is highly actionable in most sections, but it functions as a monolithic ~490-line catalog in SKILL.md with no reference files, includes several sections of basic pytest knowledge Claude already has, and offers no sequenced workflow or validation checkpoints.

Suggestions

Split reference-catalog content into bundle files (e.g. references/fixtures.md, references/mocking.md, references/hypothesis.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Cut sections that restate knowledge Claude already has — test discovery conventions, basic assertion syntax, and the elementary 'pytest -v / -s' run flags — keeping only non-obvious patterns and project-specific conventions.

Add a short sequenced workflow with checkpoints, e.g. write test → run 'pytest --lf' on failures → check 'pytest --cov --cov-report=term-missing' → act on missing lines, so users get an ordered process instead of a topic catalog.

DimensionReasoningScore

Conciseness

The body is mostly lean pattern code rather than padded prose, but it spends entire sections on pytest fundamentals Claude already knows — 'pytest automatically discovers tests following these conventions', a 'Basic Assertions' block showing 'assert value == expected', and basic run flags like 'pytest -v' and 'pytest -s'. This is more than a minor instance of over-explanation (ruling out 4) yet the bulk is legitimately useful pattern reference rather than filler (ruling out 2).

3 / 5

Actionability

Nearly every section provides concrete, executable code or commands — complete fixture examples with setup/teardown, parametrize tables, coverage commands ('pytest --cov=src --cov-report=term-missing'), and marker-based run commands. Minor gaps keep it below 5: examples reference undefined symbols (User, UserRepository, validate_email), and 'mock_email_service.send.assert_called_once()' is subtly wrong after patching the class (it needs '.return_value.send').

4 / 5

Workflow Clarity

The content is a topical reference with no sequenced workflow — there is no 'write test → run → check coverage → improve' pipeline, and no validation or feedback loop for the workflows it implies (e.g., what to do when '--cov-fail-under=80' fails). This matches anchor 3 (steps/structure present but checkpoints missing); the skill is too long (>50 lines) for the simple-skill exception to apply.

3 / 5

Progressive Disclosure

No bundle files exist, so all ~490 lines live inline in SKILL.md. Section headers provide real structure, but reference-catalog content that clearly belongs in separate files — the full run-command catalog, hypothesis property-based testing, advanced mocking — is inlined, matching anchor 3 ('content that should be separate is inline') rather than anchor 4's 'most content appropriately placed'.

3 / 5

Total

13

/

20

Passed

Description

83%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 description: it names a specific niche (pytest-based Python testing), enumerates concrete capabilities, and includes an explicit 'Use when' trigger. The main improvement opportunity is a richer trigger clause with more natural variations (unit tests, test suite, flaky tests).

Suggestions

Expand the 'Use when' clause with concrete trigger phrases, e.g. 'Use when writing or improving Python tests, setting up pytest, debugging flaky tests, or when the user mentions unit tests, test coverage, or test suites.'

Add common synonyms such as 'unit tests', 'integration tests', and 'test coverage' to the trigger keywords so the description matches more of the phrases users naturally say.

DimensionReasoningScore

Specificity

Names the domain (Python testing with pytest) and lists six concrete capability areas — 'fixtures, parametrization, mocking, coverage analysis, async testing, and test organization' — giving comprehensive coverage of the domain, matching the score-5 anchor; it is not score 4 because there are no meaningful gaps in the enumerated capabilities.

5 / 5

Completeness

Both parts are present: a clear 'what' ('Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization') and an explicit 'when' ('Use when writing or improving Python tests'). The 'when' clause is explicit but brief and generic compared to anchor 5's richer concrete trigger phrases, so it sits at anchor 4 rather than 5, and well above anchor 3 (where 'when' is missing).

4 / 5

Trigger Term Quality

Contains good natural keywords users would say ('Python tests', 'pytest', 'mocking', 'coverage', 'writing or improving') but misses common variations like 'unit tests', 'integration tests', 'test suite', or file extensions — matching anchor 4 rather than the fully comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — Python testing specifically with pytest — with distinct triggers ('Python tests', 'pytest') and minimal conflict risk; it would not plausibly fire for a non-testing or non-Python skill, matching the score-5 anchor rather than anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.