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

56%

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

Quality

Content

37%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 body is token-efficient and well-sectioned but fails on actionability and workflow clarity because its instructions are generic abstract directives with no concrete code, commands, sequence, or validation steps, and its sole resource reference points to a file that is not present in the bundle.

Suggestions

Replace the abstract instruction bullets with concrete, executable guidance: example pytest fixtures, a parameterize decorator snippet, and a mock usage pattern.

Define a real sequenced workflow (e.g., 1. write failing test -> 2. run pytest -> 3. implement -> 4. re-run until green) with an explicit validation checkpoint.

Create the referenced resources/implementation-playbook.md file (or remove the dangling reference) so progressive disclosure points to real material.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or explanations of concepts Claude already knows (no 'what is pytest' prose); every section earns its tokens assuming Claude's competence.	5 / 5
Actionability	The Instructions section offers only abstract directives ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes') with no concrete code, commands, or examples, matching the score-1 anchor of describing rather than instructing.	1 / 5
Workflow Clarity	The four instruction bullets are parallel directives with no sequence, no validation checkpoints, and no feedback loops, matching the score-1 anchor of steps being missing or incoherent.	1 / 5
Progressive Disclosure	Section structure is clear (Use when / Don't use / Instructions / Resources) with a one-level reference to resources/implementation-playbook.md, but that referenced file does not exist in the bundle and the generic instructions are content that should live in the referenced playbook, fitting the score-3 anchor.	3 / 5
	Total	10 / 20 Passed

Description

75%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 well-structured with explicit what and when clauses and concrete capability keywords, scoring consistently at 4 across dimensions. It stops short of 5 due to broad-category actions rather than enumerated concrete actions and a when-clause that lists activities instead of user-mention trigger phrases.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete capabilities ('pytest, fixtures, mocking, and test-driven development'), but these are broad categories rather than enumerated concrete actions like the score-5 anchor, placing it clearly at 4.	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...'), but the when-clause lists activities rather than the user-mention trigger pattern of the score-5 anchor.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('writing Python tests', 'setting up test suites', 'testing best practices') with good coverage, though common synonyms like 'unit tests' appear only in the body and a few natural variations are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to Python testing with pytest, a clear niche distinct from general Python or generic testing skills, with only minor overlap risk against a dedicated pytest skill.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/python-testing-patterns/SKILL.md
Commit: 3eff4af

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