python-patterns

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

Quality

57%

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%

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 thorough, action-rich Python patterns reference with strong executable examples and tooling configuration, but it is a monolithic single file that re-explains many concepts Claude already knows and offers no multi-step workflow with validation checkpoints. It is well-organized but violates progressive-disclosure and conciseness expectations for a skill of this length.

Suggestions

Split the inline reference into one-level-deep files (e.g. TYPE_HINTS.md, CONCURRENCY.md, TOOLING.md) with a concise overview and clearly signaled links in SKILL.md.

Trim explanations of basic concepts Claude already knows (EAFP, context managers, list comprehensions, decorators) and keep only the recommended/not-recommended contrasts and non-obvious guidance.

For any guidance involving batch or destructive operations (e.g. running ruff/black across a project), add explicit validate-then-proceed checkpoints to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The ~750-line body explains many concepts Claude already knows (EAFP, context managers, list comprehensions, decorators, dataclasses), which the rubric penalizes; however, the consistent recommended/not-recommended framing and the concrete tooling config add value beyond pure concept restatement, placing it at 'mostly efficient but could be tightened' rather than fully verbose.	2 / 3
Actionability	It provides extensive executable code patterns plus concrete copy-paste-ready commands ('black .', 'ruff check .', 'mypy .') and a complete pyproject.toml, matching the 'fully executable code/commands; copy-paste ready' anchor; the few undefined placeholder symbols (e.g. default_value, Config) are conventional in pattern illustrations.	3 / 3
Workflow Clarity	This is a reference catalog of patterns rather than a multi-step workflow, and there is no sequenced process with validation checkpoints or feedback loops for any risky/batch operation, fitting the 'steps listed but validation gaps / sequence present but checkpoints missing' anchor rather than anchor 3.	2 / 3
Progressive Disclosure	All content lives inline in a single ~750-line SKILL.md with no references/, scripts/, or assets/ bundle files; section headers provide structure, but substantial content (type hints, concurrency, tooling) that should be split into one-level-deep reference files is inline, matching the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 identifies the Python domain and lists relevant topic areas, but it reads as a topic enumeration rather than a statement of concrete actions and lacks any explicit 'Use when...' trigger guidance. It is competent but generic, with every dimension landing at the middle anchor.

Suggestions

Rewrite the description as concrete third-person actions, e.g. 'Reviews, refactors, and writes Pythonic code applying PEP 8, type hints, and best-practice patterns.'

Add an explicit trigger clause such as 'Use when writing, reviewing, or refactoring Python code, or designing Python packages and modules.'

Include natural user-facing keyword variations (e.g. 'Pythonic', 'type hints', 'PEP 8', 'Python best practices') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Python 应用程序') and several specific topic areas ('Python 惯用法...PEP 8 标准、类型提示...以及最佳实践'), but these are concepts/standards rather than concrete actions like 'writes', 'reviews', or 'refactors', matching the 'names domain and some actions, but not comprehensive' anchor rather than the multiple-concrete-actions anchor 3.	2 / 3
Completeness	It clearly states what the skill covers but provides no 'when to use it' guidance; per the rubric guidelines, a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'Python', 'PEP 8', 'type hints', and 'Pythonic' are natural keywords a user might say, but there are no common action-oriented variations or trigger phrases, fitting the 'some relevant keywords but missing common variations' anchor rather than the broad coverage of anchor 3.	2 / 3
Distinctiveness Conflict Risk	It is clearly Python-specific, which narrows conflict risk, but the broad framing around 'best practices' and 'idioms' with no explicit triggers could still overlap with other Python skills, matching the 'somewhat specific but could still overlap' anchor.	2 / 3
	Total	8 / 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 (751 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: xu-xiang/everything-claude-code-zh
Path: docs/ja-JP/skills/python-patterns/SKILL.md
Commit: dfbf946

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