python-pytest-patterns

pytest testing patterns for Python. Triggers on: pytest, fixture, mark, parametrize, mock, conftest, test coverage, unit test, integration test, pytest.raises.

0.95x

Quality

73%

Does it follow best practices?

Impact

68%

0.95x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/python-pytest-patterns/SKILL.md

Quality

Content

71%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 a well-organized, mostly executable pytest pattern catalog with a useful command quick-reference, but it inlines content that its own references section promises to offload, and none of those referenced bundle files actually exist. Creating the referenced files and trimming the inline catalog would materially improve it.

Suggestions

Create the referenced bundle files (references/fixtures-advanced.md, scripts/run-tests.sh, assets/pytest.ini.template, etc.) or remove the dangling references so navigation is not broken.

Move the advanced/duplicated sections (fixture scopes, pytest-mock, conftest detail) into the corresponding reference files and keep only a Quick Start plus pointers in SKILL.md.

Make code examples self-contained or clearly label the undefined helpers as placeholders so they read as fully copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with minimal prose ('Modern pytest patterns for effective testing.') and no padding about what pytest is, but it inlines a broad catalog (~190 lines) with some trivial examples (1+1==2) and duplicated mocking coverage, keeping it just below fully lean.	4 / 5
Actionability	Each section pairs a short header with copy-paste-ready code and the Quick Reference table lists concrete commands, but several examples call undefined helpers (calculate_total, double, function_using_api, create_app), leaving minor gaps that prevent a 5.	4 / 5
Workflow Clarity	This is a pattern reference rather than a multi-step workflow, and the Quick Reference gives an unambiguous catalog of runnable commands; no validation checkpoints are needed for a non-destructive reference, so it scores 4 rather than 3, but it lacks an explicit end-to-end workflow so it does not reach 5.	4 / 5
Progressive Disclosure	References are clearly signaled in a dedicated section with one-line descriptions, but the referenced bundle files (./references/.md, ./scripts/.sh, ./assets/*.template) do not exist on disk and much pattern content that belongs in those references is inlined, fitting the 'structure present but content that should be separate is inline' anchor.	3 / 5
	Total	15 / 20 Passed

Description

76%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 has strong, comprehensive trigger terms and a clear niche, but its 'what' statement is generic and lacks concrete enumerated actions. Adding two or three specific verbs would lift specificity and completeness.

Suggestions

Replace 'pytest testing patterns for Python' with concrete actions, e.g. 'Write pytest fixtures, parametrize tests, mock dependencies, and structure conftest.py.'

Keep the trigger list but consider folding it into a 'Use when...' clause so the 'when' reads as natural guidance rather than a raw keyword dump.

Dimension	Reasoning	Score
Specificity	The phrase 'pytest testing patterns for Python' names the domain but lists no concrete actions (no verbs like 'write fixtures' or 'parametrize tests'), matching the 'names domain but actions minimal or generic' anchor; it does not reach 3 because no concrete actions are enumerated.	2 / 5
Completeness	Both 'what' (pytest testing patterns for Python) and an explicit 'when' (the 'Triggers on' clause with concrete trigger phrases) are present; it stays at 4 rather than 5 because the 'what' is generic ('testing patterns') rather than enumerating concrete actions like the anchor-5 example.	4 / 5
Trigger Term Quality	'Triggers on: pytest, fixture, mark, parametrize, mock, conftest, test coverage, unit test, integration test, pytest.raises' provides comprehensive natural keywords including synonyms and tool-specific terms a user would actually say, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	'pytest testing patterns for Python' paired with pytest-specific triggers (conftest, parametrize, pytest.raises) carves a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/python-pytest-patterns/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours 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.