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

—

Does it follow best practices?

Impact

68%

0.95x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

80%

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

The body is an efficient, highly actionable pattern catalog with copy-paste code, but it lacks any sequenced workflow and its bundle references point to files that are not actually present.

Suggestions

Create the referenced bundle files (./references/*.md, ./scripts/*.sh, ./assets/*.template) or remove the dangling reference sections so signaled navigation resolves.

If a canonical test-authoring workflow is intended, add a short sequenced section (e.g. write -> parametrize -> mock -> run --lf) with a verification step to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean: terse section headers followed by executable code, with no preamble explaining what pytest is or how libraries work, so every token earns its place.	3 / 3
Actionability	Each section provides copy-paste-ready, executable pytest code, and the Quick Reference table lists concrete commands, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Content is organized by topic (fixtures, parametrize, mocking, conftest) but it is a pattern catalog without a sequenced multi-step workflow or validation checkpoints; structure is present but no process sequence is articulated.	2 / 3
Progressive Disclosure	References, scripts, and assets are clearly signaled and one level deep in dedicated sections, but the referenced files (./references/.md, ./scripts/.sh, ./assets/*.template) do not exist on disk, so the navigation points to missing bundles.	2 / 3
	Total	10 / 12 Passed

Description

72%

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, natural trigger terms and a clear niche, but its capability statement is a generic label rather than a list of concrete actions, leaving the 'what' portion thin.

Suggestions

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

Keep the strong 'Triggers on:' list but consider phrasing the usage clause as 'Use when...' for consistency with the rubric's good examples.

Dimension	Reasoning	Score
Specificity	The phrase 'pytest testing patterns for Python' names the domain and topic but does not enumerate concrete actions (e.g. 'write fixtures', 'parametrize tests', 'mock dependencies'), matching the 'names domain and some actions' anchor rather than the multi-action level 3.	2 / 3
Completeness	It states what ('pytest testing patterns') and when (explicit 'Triggers on:' list), but the 'what' is a generic domain label rather than concrete capabilities, so it falls short of the level-3 'clearly answers both with concrete what' anchor.	2 / 3
Trigger Term Quality	'Triggers on: pytest, fixture, mark, parametrize, mock, conftest, test coverage, unit test, integration test, pytest.raises' gives broad, natural coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	It targets a clear pytest niche with distinct, specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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
Commit: 26d37ce

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