python-patterns

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

Quality

63%

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/zh-CN/skills/python-patterns/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

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 comprehensive, highly actionable Python patterns reference with executable examples throughout and good section structure. Its main weaknesses are the absence of explicit validation checkpoints in any workflow and a monolithic single-file layout with no progressive disclosure into reference files.

Suggestions

Add explicit validation checkpoints/feedback loops where operations carry risk (e.g., after type-annotating, run 'mypy .' and fix reported errors before proceeding) to raise workflow clarity.

Split bulk reference material into separate bundle files (e.g., references/tooling.md for command/config references, references/antipatterns.md) and link to them from SKILL.md to improve progressive disclosure.

Trim the basic-concept restatements (e.g., explanations of EAFP vs LBYL, why mutable defaults are bad) since Claude already knows these, keeping only the contrasting code examples.

Dimension	Reasoning	Score
Conciseness	The body is predominantly lean annotated code examples with brief captions and little prose explaining concepts Claude already knows, with only minor instances of basic-concept restatement (e.g., EAFP/LBYL, mutable defaults), matching anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	It provides pervasive, copy-paste-ready executable code and commands covering the common cases across typing, context managers, dataclasses, decorators, concurrency, and tooling, directly matching the anchor 5 example.	5 / 5
Workflow Clarity	Sections are clearly sequenced but there are no explicit validation checkpoints or feedback loops embedded in any process, and validation tools (mypy, pytest) appear only as listed commands rather than as steps, matching anchor 3.	3 / 5
Progressive Disclosure	The content is well-organized with clear section headers, but at ~750 lines it is a monolithic inlined file with no external references, and bulk reference material (tooling commands, full pyproject.toml, antipattern catalog) that belongs in separate files is inlined, matching anchor 3.	3 / 5
	Total	15 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 names a clear Python-development niche with several relevant topic areas and natural trigger terms, but it is missing an explicit "Use when..." trigger clause and is phrased as practices/topics rather than concrete actions. Adding trigger guidance and discrete capabilities would lift the capped dimensions.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should activate this skill (e.g., 'Use when writing, reviewing, or refactoring Python code, or designing Python packages').

Reframe capabilities as concrete actions rather than topic areas (e.g., 'Apply PEP 8 style, add type hints, refactor to idiomatic patterns') to raise specificity.

Include natural synonyms and file extensions users actually say (e.g., '.py files', 'Python linting', 'type annotations') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete capability areas ("Pythonic 惯用法", "PEP 8 标准", "类型提示") but frames them as topics/best practices rather than discrete executable actions, so it stops at anchor 3 rather than listing several specific concrete actions.	3 / 5
Completeness	It clearly states the "what" but provides no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant natural terms a Python user might say ("Pythonic 惯用法", "PEP 8", "类型提示"), but omits common variations and synonyms such as ".py", "Python code review", or "linting", matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	It targets a fairly specific Python style/patterns niche with low conflict risk against non-Python skills, but lacks distinct explicit trigger phrases that would fully separate it from a generic Python coding skill, so it sits at anchor 4 rather than 5.	4 / 5
	Total	13 / 20 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: affaan-m/ECC
Path: docs/zh-CN/skills/python-patterns/SKILL.md
Commit: e04ea0b

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.