CtrlK
BlogDocsLog inGet started
Tessl Logo

python-patterns

Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications. Use when writing or reviewing Python code and idiomatic structure, typing, or PEP 8 is in question.

60

Quality

71%

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 ./skills/python-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 thorough, highly actionable Python patterns reference with executable code throughout, but it is verbose for a skill, explains basic concepts Claude already knows, and inlines everything into a single monolithic file with no progressive disclosure via bundle references.

Suggestions

Trim explanations of concepts Claude already knows (e.g., the prose around EAFP/LBYL and 'readability counts') so each section leads with the pattern, keeping only the good/bad code pairs.

Move the large pyproject.toml configuration block and the full pattern catalog into reference files (e.g., references/tooling.md, references/patterns.md) and link to them from SKILL.md to improve progressive disclosure.

Deduplicate the timer example (it appears in both Context Managers and Decorators) or cross-reference it to reduce token cost.

DimensionReasoningScore

Conciseness

The catalog is mostly efficient with code earning its place, but it explains concepts Claude already knows ('Python prioritizes readability', 'Easier to Ask Forgiveness Than Permission', LBYL) and repeats the timer decorator in two sections, matching 'mostly efficient but includes some unnecessary explanation' rather than the lean 4 or 5.

3 / 5

Actionability

Provides extensive executable, copy-paste-ready code across comprehensions, dataclasses, decorators, concurrency, context managers, and tooling commands with concrete examples covering the common cases, matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

This is a reference catalog rather than a multi-step process; the 'When to Activate' list and section structure give a rough sequence but there are no validation checkpoints or feedback loops, matching 'steps listed but validation gaps; checkpoints missing or implicit' and capping below 4.

3 / 5

Progressive Disclosure

No bundle files exist, so all content (including tooling config and the full pattern catalog) is inlined into one ~750-line SKILL.md with no external references signaled; sections are organized but content that could be split is inline, matching the 'some structure but could be better organized' anchor.

3 / 5

Total

14

/

20

Passed

Description

78%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 is specific, third-person, and clearly answers both what the skill does and when to use it with an explicit 'Use when...' trigger clause. It is among the stronger examples, with only minor keyword-coverage gaps keeping trigger and completeness at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — 'Pythonic idioms, PEP 8 standards, type hints, and best practices' — naming the domain and multiple specific actions, with only minor coverage gaps, matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

Provides a clear 'what' (idioms, PEP 8, type hints, best practices) and an explicit 'when' ('Use when writing or reviewing Python code and idiomatic structure, typing, or PEP 8 is in question'), but the 'when' could be slightly more specific, fitting the 'both what and when; when could be more explicit' anchor.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('writing or reviewing Python code', 'typing', 'PEP 8') giving good keyword coverage, but misses common synonyms and file extensions like '.py' or 'linting/formatting', so it sits below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear Python-specific niche with distinct triggers (PEP 8, type hints, Pythonic idioms) and minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

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.