python-patterns

Python-specific design patterns and best practices including protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization. Use when working with Python code to apply Pythonic patterns.

Quality

70%

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

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 content is a strong, mostly executable Python patterns reference with good organization and lean code-first sections. Its weaknesses are the lack of any multi-step workflow (it is a catalog, so validation/sequencing is absent) and a monolithic inline structure that could benefit from splitting detailed sections into referenced files.

Suggestions

Trim the "Benefits"/"Features" bullet lists that restate well-known Python behavior (e.g. dataclass auto-generated methods) to tighten conciseness.

Split the largest sections (e.g. Async/Await, Type Hints, Package Organization) into reference files linked one level deep from SKILL.md to improve progressive disclosure.

Replace `pass`/`# implementation` stubs in the Repository examples with minimal but real bodies so every example is fully executable.

Dimension	Reasoning	Score
Conciseness	The body is mostly code with brief one-line intros and is not padded with explanations of basic concepts, but the recurring "Benefits"/"Features" bullet lists restate things Claude already knows (e.g. dataclass auto-generated methods), keeping it just below lean.	4 / 5
Actionability	Concrete, copy-paste-ready Python examples cover the common cases for each pattern, with only minor gaps where implementations are stubbed with `pass` or `# implementation` (Repository, find_by_id).	4 / 5
Workflow Clarity	This is a pattern catalog rather than a multi-step workflow, so there is no sequenced process or validation checkpoints; the "When to Use This Skill" list provides unordered triggers but no executable sequence.	3 / 5
Progressive Disclosure	Content is well-sectioned with clear headers, but at ~415 lines everything is inlined in SKILL.md with no bundle files or one-level-deep references; sizable sections (async, type hints, package organization) could be split out for navigation.	3 / 5
	Total	14 / 20 Passed

Description

75%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 well-constructed: third-person voice, explicit "Use when" trigger, and a comprehensive list of specific Python pattern domains. The main weakness is that the "when" clause is broad and capabilities are named as topics rather than actions.

Suggestions

Make the trigger clause more specific, e.g. "Use when designing Python APIs, refactoring Python code, or applying Pythonic idioms like protocols, dataclasses, or async/await."

Reframe capabilities as actions where possible (e.g. "apply structural typing with Protocol, model data with dataclasses") to strengthen specificity.

Add a file-extension cue such as ".py / .pyi files" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists seven concrete capabilities ("protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization") giving comprehensive coverage, but they are framed as noun-topics rather than verb-actions, keeping it just below a 5.	4 / 5
Completeness	Both "what" (Python-specific design patterns and best practices including ...) and "when" ("Use when working with Python code to apply Pythonic patterns") are present and explicit, but the "when" trigger is broad and could be more specific.	4 / 5
Trigger Term Quality	Natural terms a user would say appear ("Python", "design patterns", "Pythonic patterns", "async/await", "decorators", "working with Python code"), but it lacks synonyms and file extensions like .py that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The Python-specific niche ("Python-specific design patterns", "Pythonic patterns") is clear with minimal conflict risk, with only minor overlap potential against a general design-patterns or clean-code skill.	4 / 5
	Total	16 / 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/python-patterns/SKILL.md
Commit: ca185ef

Reviewed: 1 day 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.