python-patterns

Pythonic 惯用法、PEP 8 标准、类型提示，以及构建稳健、高效且可维护 Python 应用的最佳实践。

Quality

61%

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-patterns/SKILL.md

Quality

Content

65%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 content is highly actionable with concrete, executable examples and strong tooling coverage, but it functions as a monolithic catalog of familiar Python idioms rather than a lean skill with progressive disclosure or sequenced workflows. It earns top marks for actionability and mid marks elsewhere.

Suggestions

Trim or move basic idioms Claude already knows (e.g., is vs ==, mutable default args, list-comprehension basics) into a separate reference file to improve conciseness.

Add a brief "Quick start" or decision workflow with validation steps for tasks like setting up tooling or applying lint/type checks, to strengthen workflow clarity.

Split detailed sections (type hints, concurrency, packaging) into referenced files and keep SKILL.md as a concise overview to enable proper progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is accurate and code-forward, but a large share of it restates widely-known Python conventions (EAFP, mutable default args, is vs ==, __slots__) that Claude already knows, so it could be tightened considerably.	2 / 3
Actionability	It provides fully executable Good/Bad code pairs, concrete tooling commands (black, ruff, mypy, pytest), and a complete pyproject.toml, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	Content is well-organized into sections and lists when to enable the skill, but there is no sequenced multi-step workflow with validation checkpoints or feedback loops, which leaves workflow clarity mid-level.	2 / 3
Progressive Disclosure	No bundle files exist and the skill makes no external references, so all material lives inline in one ~750-line document that could be split into separate reference files for better disclosure.	2 / 3
	Total	9 / 12 Passed

Description

57%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 clearly conveys the skill's Python-focused niche and is reasonably distinguishable, but it is topic-oriented rather than action-oriented and omits an explicit "Use when..." trigger clause. It scores solidly at the mid level across most dimensions.

Suggestions

Rewrite the description to lead with concrete actions (e.g., "Writes, reviews, and refactors Python code...") instead of a noun list, to lift specificity.

Add an explicit trigger clause such as "Use when writing, reviewing, or refactoring Python code, or when applying PEP 8 and type hints" to raise completeness.

Include natural English trigger variants (e.g., "Python best practices," "Pythonic code") alongside the Chinese terms for broader trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names a domain and specific topics ("Pythonic 惯用法、PEP 8 标准、类型提示") but describes topical nouns rather than concrete actions the skill performs, so it stops short of listing multiple specific actions.	2 / 3
Completeness	It clearly states what the skill covers (idioms, PEP 8, type hints, best practices) but lacks any "Use when..." or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes relevant terms like PEP 8 and type hints a user might say, but the Chinese-mixed phrasing misses common variations such as "Python best practices" or "refactoring Python," giving only moderate coverage.	2 / 3
Distinctiveness Conflict Risk	The Python-specific anchoring around PEP 8, type hints, and Pythonic idioms forms a clear niche with distinct triggers unlikely to conflict with other skills, despite a slightly generic "best practices" framing.	3 / 3
	Total	9 / 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 (750 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-patterns/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.