CtrlK
BlogDocsLog inGet started
Tessl Logo

python-patterns

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

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 content is highly actionable with abundant executable examples and solid organization, but it is a long monolithic reference that re-teaches known concepts and lacks progressive disclosure via separate files.

Suggestions

Split the large reference into bundle files under references/ (e.g., type hints, concurrency, tooling) and keep SKILL.md as an overview with one-level-deep links.

Trim sections that re-explain concepts Claude already knows (basic decorators, dataclasses, asyncio basics) to improve token efficiency.

Add a brief decision workflow (e.g., pick the concurrency model by I/O-bound vs CPU-bound) with explicit checkpoints instead of only catalogued patterns.

DimensionReasoningScore

Conciseness

Mostly efficient code examples with brief commentary, but the ~745-line reference re-teaches concepts Claude already knows (basic type hints, dataclasses, decorators, asyncio) and the repetitive Good/Bad framing could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready code and commands across many topics (type hints, context managers, concurrency, pyproject.toml, tool commands) with Good/Bad pairs covering common cases.

5 / 5

Workflow Clarity

As a patterns reference rather than a multi-step process, it is well-organized with an activation-trigger section and clear topical sections plus a quick-reference table, though it lacks explicit multi-step workflow sequencing.

4 / 5

Progressive Disclosure

No bundle files exist and all content is inlined in a single ~745-line SKILL.md with good section headers but no file splitting or references for content that could live in separate files.

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 clearly states the domain and a few concrete facets but provides no explicit trigger guidance, which caps its completeness. It is reasonably distinct as a Python-specific skill.

Suggestions

Add an explicit 'Use when...' clause in Japanese (e.g., 'Pythonコードを書く、レビューする、リファクタリングするときに使用') to answer both what and when.

Replace the generic 'ベストプラクティス' framing with concrete actions (lint, format, type-check, refactor) to lift specificity.

Include natural user-facing trigger terms like '.py', '型ヒント', 'リント', 'フォーマット' for better trigger coverage.

DimensionReasoningScore

Specificity

Names the Python domain plus concrete facets like '型ヒント' and 'PEP 8標準', but the actions ('ベストプラクティス', 'アプリケーションを構築する') stay generic rather than listing concrete operations like lint, format, or refactor.

3 / 5

Completeness

The 'what' is clear (idioms, PEP 8, type hints for robust/efficient/maintainable Python apps) but the 'when' is entirely absent with no 'Use when...' clause, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Contains relevant keywords ('Python', '型ヒント', 'Pythonic イディオム') but misses natural phrases a user would say such as reviewing, refactoring, or writing Python code, which only appear in the body, not the description.

3 / 5

Distinctiveness Conflict Risk

The Python-specific patterns niche (idioms, PEP 8, type hints) is mostly distinct from other skills, with only minor overlap risk against general coding skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (750 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
Reviewed

Table of Contents

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.