python-testing

使用pytest的Python测试策略，包括TDD方法、夹具、模拟、参数化和覆盖率要求。

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with extensive executable pytest examples and commands, but it is an over-long monolithic reference that re-teaches pytest basics Claude already knows. Splitting into focused reference files and trimming beginner material would improve conciseness and progressive disclosure.

Suggestions

Trim the basic assertion catalog and trivial fixture examples that restate knowledge Claude already has; keep only non-obvious patterns.

Split the large body into one-level-deep reference files (e.g. fixtures.md, mocking.md, async.md) with a concise overview in SKILL.md linking to them.

Add an explicit end-to-end testing workflow with validation checkpoints (write failing test → run `pytest -x` → implement → re-run until green → check `pytest --cov`).

Dimension	Reasoning	Score
Conciseness	Mostly organized as code reference, but it spends substantial tokens teaching pytest basics Claude already knows — e.g. the assertion catalog ("assert result == expected", "assert result is True", membership/comparison forms) and trivial fixture examples. Not a 1 because it is reference-style rather than verbose prose fluff; not a 3 because much of this beginner material could be trimmed.	2 / 3
Actionability	Provides abundant executable, copy-paste-ready code and concrete commands throughout — e.g. `pytest --cov=mypackage --cov-report=term-missing`, full `@pytest.fixture` and `@patch` examples, and complete pytest.ini/pyproject.toml configs. Not a 2 because examples are complete and runnable rather than pseudocode.	3 / 3
Workflow Clarity	The TDD section gives a clear red/green/refactor sequence ("红...绿...重构"), but the skill is otherwise a reference catalog without a coherent end-to-end workflow with explicit validation checkpoints for testing a feature. Not a 1 because the TDD loop and run-commands provide some sequence; not a 3 because checkpoints are implicit and scattered rather than a unified validated workflow.	2 / 3
Progressive Disclosure	The ~810-line body is a single monolithic file with well-organized sections but no bundle files (references/scripts/assets are empty) and no split reference files; content that could live separately (mocking, fixtures, async testing) is inline. Not a 1 because sections are clearly organized; not a 3 because the large monolith should be split with one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 specific and well-scoped to pytest Python testing with a clear niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness and weakens trigger-term quality. Adding natural-language activation triggers would raise the two lower dimensions.

Suggestions

Append a 'Use when...' clause with natural triggers, e.g. 'Use when writing or reviewing Python tests, designing a pytest test suite, or improving test coverage.'

Broaden trigger-term coverage with common user phrasings such as 'unit tests', 'test coverage', 'mocking', and '.py test files'.

Reframe '夹具' toward more natural Chinese phrasing (e.g. 'fixture/测试夹具') so trigger terms match what users actually say.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities — "TDD方法、夹具、模拟、参数化和覆盖率要求" (TDD, fixtures, mocking, parameterization, coverage) — naming both the domain and specific testing techniques. Not the level below (2), which would name only the domain and some actions without this breadth.	3 / 3
Completeness	Clearly states what the skill does ("使用pytest的Python测试策略..."), but provides no 'Use when...' clause or equivalent explicit trigger guidance for when to activate it. Per rubric guidelines, a missing explicit trigger caps completeness at 2; it is not a 1 because the 'what' is concrete.	2 / 3
Trigger Term Quality	Contains relevant terms a user might say ("pytest", "Python测试", "TDD", "覆盖率"), but misses common natural variations (e.g. "unit tests", "test coverage", "mock") and offers no explicit trigger phrasing. Not a 3 because keyword coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	Scoped to pytest-based Python testing with specific terminology, giving it a clear niche unlikely to conflict with other skills. Not a 2 because the terms are specific enough (pytest, TDD, coverage) to avoid overlap with generic coding skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (817 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/everything-claude-code
Commit: 4130457

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.