python-patterns

Pythonic イディオム、PEP 8標準、型ヒント、堅牢で効率的かつ保守可能なPythonアプリケーションを構築するためのベストプラクティス。

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 thorough executable examples and a useful quick reference, but it is a long monolithic catalog that re-explains basics and uses no progressive disclosure to offload detail into reference files. Splitting large topical sections into references would improve both conciseness and progressive disclosure.

Suggestions

Move the larger topical blocks (concurrency, packaging, decorators, memory/performance) into reference files and keep SKILL.md as a concise overview with one-level-deep links.

Trim re-explanations of fundamentals Claude already knows (EAFP, readability, mutable defaults) down to the actionable Good/Bad pair.

For sections that involve tooling or batch operations, add explicit validate/run checkpoints so the reference can also serve as a sequenced workflow.

Dimension	Reasoning	Score
Conciseness	Each section is reasonably tight, but the overall body re-teaches fundamentals Claude already knows (readability priority, EAFP meaning, mutable-default pitfalls) across ~745 lines, making it mostly efficient but padded rather than lean.	2 / 3
Actionability	Provides extensive executable, type-hinted code, concrete tool commands (black, ruff, mypy, pytest), a complete pyproject.toml, and a quick-reference table — copy-paste ready throughout.	3 / 3
Workflow Clarity	Organized into clear sections with a 'when to activate' list, but it is a reference catalog rather than a sequenced workflow, so there are no explicit validation checkpoints or feedback loops to reach anchor 3.	2 / 3
Progressive Disclosure	No bundle files exist and all content is inlined in a single monolithic ~745-line file; section organization keeps it above level 1, but the large catalog is not split into one-level-deep references as anchor 3 requires.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 clearly Python-scoped and distinctive, but it reads as a topic basket rather than a list of concrete actions and omits any explicit 'Use when…' trigger guidance. Adding trigger phrasing and concrete verbs would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when…' clause naming natural user triggers (e.g., writing, reviewing, refactoring, or designing Python code).

Replace the topic-list phrasing with concrete actions the skill performs, mirroring the 'Extract… fill… merge…' style.

Add common user phrasings ('Python code', 'Pythonic', 'type hints') alongside the technical terms to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Python domain with concrete facets ('Pythonic イディオム、PEP 8標準、型ヒント') but presents a basket of concerns rather than multiple distinct concrete actions, so it falls short of anchor 3.	2 / 3
Completeness	It clearly states what the skill covers, but there is no 'Use when…' trigger clause, so the 'when' guidance is entirely missing and completeness is capped at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes real terms ('Python', '型ヒント', 'PEP 8') but lacks natural user phrasings and common variations like 'writing Python code' or 'Python review'; not a level-1 jargon-only description but coverage is incomplete.	2 / 3
Distinctiveness Conflict Risk	Scoped specifically to Python development with PEP 8 / type-hint / idiom triggers, giving it a clear niche unlikely to conflict with non-Python skills.	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: 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.