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

48%

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

The canonical home for this skill is python-testing-patterns in rmyndharis/antigravity-skills

Quality

Content

18%Scale 1-5

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

This skill is essentially a hollow shell — it has a title and topic list but contains no actual testing knowledge, patterns, code examples, or actionable guidance. All substance is deferred to a resource file that doesn't exist in the bundle. The instructions section consists of generic boilerplate that could apply to any skill and provides nothing specific to Python testing.

Suggestions

Add concrete, executable pytest examples covering the core patterns: basic test structure, fixtures, mocking with unittest.mock/pytest-mock, and parameterization — these are the minimum for a testing skill.

Replace the generic instruction bullets with a specific TDD workflow: write test → run and see failure → implement → run and verify pass → refactor, with actual pytest commands (e.g., `pytest -x -v test_module.py`).

Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns in the SKILL.md itself, since the current content provides zero actionable guidance.

Remove the padded 'Use this skill when' list (10 items) and 'Do not use this skill when' section — these consume tokens without adding value Claude can act on.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections are padded with obvious items Claude doesn't need. The instructions section is generic boilerplate ('Clarify goals, constraints, and required inputs') that adds no testing-specific value. However, it's not excessively verbose overall.	3 / 5
Actionability	There is zero concrete, executable guidance — no code examples, no specific commands, no pytest patterns, no fixture examples, no mocking examples. The instructions are entirely vague platitudes like 'Apply relevant best practices and validate outcomes.' Everything actionable is deferred to a resource file that doesn't exist in the bundle.	1 / 5
Workflow Clarity	There is no workflow, no sequenced steps, no validation checkpoints. The four bullet points in Instructions are generic meta-instructions that could apply to any skill, not a testing workflow. No TDD cycle, no test-run-fix loop, nothing specific to testing processes.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure in theory. However, the bundle shows no such file exists, the SKILL.md itself contains essentially no substantive content to serve as an overview, and the reference is a single generic pointer rather than well-signaled topic-specific links.	2 / 5
	Total	7 / 20 Passed

Description

78%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.

This is a solid skill description that clearly communicates both what the skill does and when to use it. Its main weakness is that the 'what' portion lists concepts and tools (pytest, fixtures, mocking) rather than concrete actions (e.g., 'generate test files', 'create mock objects', 'write parametrized tests'). The trigger terms are good but could be expanded with common synonyms and related terms.

Suggestions

Replace abstract concepts with concrete actions, e.g., 'Generate pytest test files, create fixtures and conftest configurations, mock dependencies, and structure test suites' instead of 'Implement comprehensive testing strategies'.

Add more trigger term variations such as 'unit tests', 'integration tests', 'test coverage', 'conftest', 'parametrize', or 'assert' to improve matching.

Dimension	Reasoning	Score
Specificity	Names the domain (testing) and mentions specific tools/concepts like pytest, fixtures, mocking, and TDD, but these are more like category labels than concrete actions. It doesn't describe specific actions like 'generate test files', 'create fixture configurations', or 'mock external dependencies'.	3 / 5
Completeness	Clearly answers both 'what' (implement comprehensive testing strategies with pytest, fixtures, mocking, and TDD) and 'when' (Use when writing Python tests, setting up test suites, or implementing testing best practices) with explicit trigger phrases.	5 / 5
Trigger Term Quality	Includes good natural keywords like 'pytest', 'fixtures', 'mocking', 'test-driven development', 'Python tests', 'test suites', and 'testing best practices'. Missing some natural variations like 'unit tests', 'integration tests', 'test coverage', 'conftest', or 'parametrize'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct by specifying Python/pytest testing specifically, which narrows the scope well. Minor overlap risk with general Python coding skills or broader testing skills in other languages, but the pytest and Python specificity helps differentiate.	4 / 5
	Total	16 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/python-testing-patterns/SKILL.md
Commit: 57c135b

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