CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-testing-patterns

Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.

Quality

72%

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 ./plugins/python-development/skills/python-testing-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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 skill delivers concrete, pattern-focused code examples and a genuine two-file reference tier, but spends substantial tokens re-teaching testing fundamentals Claude already knows and never presents the testing workflow (especially TDD) its description promises. Structure and actionability are solid; conciseness and workflow sequencing are the weak points.

Suggestions

Delete the 'Core Concepts' section — definitions of unit/integration tests, the AAA pattern, and test isolation are knowledge Claude already has; replace with a one-line pointer to references/details.md if needed.

Add an explicit testing workflow, e.g. the TDD red-green-refactor cycle (write failing test → run pytest to confirm failure → implement → run to green → refactor), since the description prominently promises TDD but no sequence appears anywhere in the body.

Trim token-heavy padding: collapse the good/bad test-name examples into one compact pattern, and remove 'pass'-body marker boilerplate and time.sleep demonstrations, keeping one minimal example per pattern.

DimensionReasoningScore

Conciseness

The 'Core Concepts' section spends ~25 lines defining unit/integration/functional tests, the AAA pattern, and test isolation — concepts Claude already knows — and the good/bad test-name examples with 'pass' bodies plus marker boilerplate pad the file further.

2 / 5

Actionability

Provides concrete, mostly executable code: retry tests with mock side_effect sequences and call_count assertions, freezegun time-travel examples, and copy-paste-ready coverage commands. Minor gaps remain — ServiceWithRetry, create_token, and Token are undefined, and pytest/os imports are missing in some examples.

4 / 5

Workflow Clarity

The body is a concept and pattern catalog with no ordered sequence; despite the description prominently promising test-driven development, no red-green-refactor workflow or any multi-step testing process is presented, leaving only the implicit write-then-run of Quick Start.

2 / 5

Progressive Disclosure

Both references are real, one level deep, and clearly signaled (the advanced-patterns pointer enumerates its topics), keeping the body at overview-plus-common-patterns altitude. Minor gaps: the details.md pointer sits awkwardly mid-document, the 'detailed' vs 'advanced' file split is fuzzy, and body mocking content overlaps details.md Pattern 4.

4 / 5

Total

12

/

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 with a clear what and an explicit, multi-clause when covering natural trigger phrases. It is specific to the Python-testing niche, with only minor gaps in keyword variations and slight genericness in the lead phrase.

DimensionReasoningScore

Specificity

Names several specific items — 'pytest, fixtures, mocking, and test-driven development', 'writing Python tests', 'setting up test suites' — though the lead verb 'Implement comprehensive testing strategies' is generic and coverage areas like parameterization and CI are absent.

4 / 5

Completeness

Explicitly answers both what ('Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development') and when ('Use when writing Python tests, setting up test suites, or implementing testing best practices') with concrete trigger clauses.

5 / 5

Trigger Term Quality

'writing Python tests', 'pytest', 'test suites', 'mocking', and 'test-driven development' are phrases users naturally say, but common variations like 'unit tests', 'integration tests', and 'test coverage' are missing.

4 / 5

Distinctiveness Conflict Risk

Python/pytest testing is a clear niche with distinct triggers, but the broad 'implementing testing best practices' clause creates minor overlap risk with general code-quality or debugging skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/python-development/skills/python-testing-patterns/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.