python-patterns

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

Install with Tessl CLI

npx tessl i github:affaan-m/everything-claude-code --skill python-patterns

What are skills?

Overall
score

61%

Review — 49%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

33%

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 identifies the Python domain and mentions specific standards (PEP 8, type hints), but lacks concrete actions and completely omits trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill over others. The Japanese language is fine, but the content needs explicit selection criteria.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Python code review', 'PEP 8', 'type hints', 'refactor Python', 'Pythonic', '.py files'

Replace abstract 'best practices' with concrete actions like 'Review Python code for PEP 8 compliance, add type annotations, refactor to Pythonic idioms'

Include common user phrases in both Japanese and English to improve trigger matching (e.g., 'コードレビュー', 'リファクタリング', 'Python style')

Dimension	Reasoning	Score
Specificity	Names the domain (Python) and mentions some concepts (Pythonic idioms, PEP 8, type hints, best practices), but doesn't list concrete actions like 'refactor code', 'add type annotations', or 'review for PEP 8 compliance'.	2 / 3
Completeness	Describes what the skill covers (Python best practices) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Python', 'PEP 8', 'type hints' (型ヒント), but missing common user phrases like 'Python code review', 'refactor', 'clean code', 'linting', or file extensions like '.py'.	2 / 3
Distinctiveness Conflict Risk	Python-specific which helps, but 'best practices' and 'maintainable applications' are broad enough to potentially overlap with general coding skills or other Python-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

65%

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

This is a solid Python patterns reference with excellent actionable code examples covering type hints, error handling, decorators, and concurrency. The main weaknesses are its length (could be split into focused sub-documents) and some unnecessary explanatory prose that Claude doesn't need. The content serves well as a reference but lacks workflow structure for when to apply which patterns.

Suggestions

Split advanced topics (並行処理パターン, パッケージ構成) into separate linked files to reduce main document length

Remove explanatory sentences like 'Pythonは可読性を優先します' - Claude knows this; keep only the code examples and brief labels

Add a decision workflow: 'When to use dataclass vs NamedTuple vs regular class' with a simple decision tree

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some explanatory text that Claude already knows (e.g., 'Pythonは可読性を優先します', explanations of what EAFP means). Some sections could be tightened, though most code examples are lean.	2 / 3
Actionability	Excellent executable code examples throughout - all Python snippets are copy-paste ready with proper imports, type hints, and complete implementations. The tool commands section provides specific CLI commands.	3 / 3
Workflow Clarity	This is primarily a reference/patterns document rather than a workflow guide. The 'いつ有効化するか' section lists triggers but lacks sequenced steps. For a patterns reference, this is acceptable, but there are no validation checkpoints for the development workflows mentioned.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and a quick reference table, but it's a monolithic document (~400 lines) that could benefit from splitting advanced topics (concurrency, packaging) into separate files with links from the main skill.	2 / 3
	Total	9 / 12 Passed

Validation

91%

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 — 10 / 11 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	10 / 11 Passed

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