python-testing

使用 pytest、TDD 方法论、固件（Fixtures）、模拟（Mocking）、参数化及覆盖率要求的 Python 测试策略。

Quality

66%

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 ./docs/ja-JP/skills/python-testing/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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

The body is highly actionable with executable examples but is a verbose monolithic reference that re-teaches pytest basics Claude already knows and keeps everything inline rather than progressively disclosing detail into separate files. Tightening basic sections and splitting reference material would most improve it.

Suggestions

Cut the introductory assertion basics (assert 2+2==4, truthy/falsy, == / != comparisons) that Claude already knows; keep only non-obvious patterns like pytest.raises match, autospec, and PropertyMock.

Split large reference blocks (Fixtures, Mocking, Configuration) into separate referenced files (e.g. FIXTURES.md, MOCKING.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add explicit validation checkpoints to the TDD workflow (e.g. 'Run pytest to confirm RED fails, then implement, then re-run to confirm GREEN') to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The ~815-line body re-teaches basic pytest concepts Claude already knows (assert 2+2==4, assert result==expected, truthy/falsy, basic fixtures and parametrize), padding the context window with material that does not assume Claude's competence, matching the 'verbose; explains concepts Claude knows' anchor; not above 1 because this is a full beginner tutorial far beyond minor tightening, and the scale floor is 1.	1 / 3
Actionability	It provides many fully executable, copy-paste-ready code blocks plus concrete shell commands (pytest --cov, pytest -m "not slow", pytest --lf) and complete config files, matching the 'fully executable code/commands' anchor; not 2 because examples are real complete code rather than pseudocode, and there is no higher anchor.	3 / 3
Workflow Clarity	The TDD RED/GREEN/REFACTOR cycle is sequenced and 'Running tests' is listed, but explicit validation checkpoints (e.g. 'run pytest to confirm the test fails before implementing') are missing or only implicit, matching the 'steps listed but validation gaps' anchor; not 3 because no explicit validate-then-proceed feedback loop is stated, not 1 because a clear multi-step sequence is present.	2 / 3
Progressive Disclosure	The skill is monolithic — 800+ lines of reference content (fixtures, mocking, config) all inline with no bundle files or external references, though sections are well-organized with clear headers and a quick-reference table, matching the 'content that should be separate is inline' anchor; not 3 because nothing is split into separate files and it is far over the 50-line simple-skill threshold, not 1 because organization is clear with no deeply nested references.	2 / 3
	Total	8 / 12 Passed

Description

82%Weight 40%Scale 1-3

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-targeted with strong natural trigger terms and a clear niche, but it omits an explicit 'Use when...' trigger clause, which caps its completeness. Adding a use-when clause would lift the weakest dimension.

Suggestions

Append an explicit trigger clause such as 'Use when writing or reviewing Python tests, setting up a pytest suite, or applying TDD.' to raise completeness from 2 to 3.

Mirror common user phrasings (e.g. 'unit tests', 'test coverage', 'test fixtures') to broaden trigger-term coverage further.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete techniques — "pytest、TDD 方法论、固件（Fixtures）、模拟（Mocking）、参数化及覆盖率要求" — naming several specific capabilities rather than vague actions, matching the 'lists multiple specific concrete actions' anchor; not 2 because it is comprehensive across many actions, not just a domain plus a few.	3 / 3
Completeness	It clearly states what the skill does (Python testing strategy with the listed techniques) but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 (has what, when is missing/implied); not 3 because no explicit when-trigger is stated.	2 / 3
Trigger Term Quality	It uses natural terms a user would actually say when requesting Python testing help — pytest, TDD, fixtures, mocking, parameterization, coverage — giving good coverage of common variations, matching the top anchor; not 2 because these span multiple natural phrasings rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	The pytest-specific Python-testing niche (with TDD, fixtures, mocking) is clearly distinct from non-testing or other-language skills and unlikely to trigger for the wrong skill, matching the 'clear niche with distinct triggers' anchor; not 2 because the domain and tooling are narrowly specific.	3 / 3
	Total	11 / 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
skill_md_line_count	SKILL.md is long (816 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: docs/ja-JP/skills/python-testing/SKILL.md
Commit: dfbf946

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