CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

51

Quality

57%

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

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 body is a thorough, highly actionable Python reference with strong executable examples, but it is over-long for a skill and teaches basic concepts Claude already knows. It is a monolithic single file with no progressive disclosure into bundle references.

Suggestions

Trim sections covering basic concepts Claude already knows (e.g. simple list comprehensions, manual vs context-manager file handling) and keep only genuinely non-obvious idiomatic guidance to improve conciseness.

Split large reference material into bundle files under references/ (e.g. tool-config.md, concurrency-patterns.md) and link to them from a lean overview in SKILL.md to improve progressive disclosure.

Add a short "Apply these patterns" workflow with an explicit verify step (e.g. run ruff/mypy/pytest after refactoring) to raise workflow clarity for code-change tasks.

DimensionReasoningScore

Conciseness

The ~745-line body teaches many concepts Claude already knows (list comprehensions, decorators, context managers, dataclasses, mutable-default-args); individual examples are tidy but the overall volume could be tightened considerably.

2 / 3

Actionability

It provides abundant complete, executable code with Good/Bad comparisons, concrete tool commands (black, ruff, mypy, pytest), and a real pyproject.toml configuration that is copy-paste ready.

3 / 3

Workflow Clarity

This is a patterns catalog rather than a multi-step workflow, so there is no sequenced process or validation checkpoints; the "何时激活" section gives triggers but no procedural flow.

2 / 3

Progressive Disclosure

All content lives in one monolithic 745-line file with no references/scripts/assets split out; sections are well-organized but content that could be separate (e.g. tool config, advanced patterns) is inline.

2 / 3

Total

9

/

12

Passed

Description

50%

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 identifies the Python domain and key subtopics but reads as a topic list rather than a concrete, trigger-rich summary. It lacks any explicit "Use when…" guidance, which limits both completeness and trigger quality.

Suggestions

Add an explicit "Use when…" clause naming natural triggers, e.g. "Use when writing, reviewing, or refactoring Python code, or when the user mentions Python, PEP 8, type hints, or Pythonic style."

Replace abstract topic phrasing with concrete actions (e.g. "Apply PEP 8 formatting, add type hints, refactor to idiomatic patterns") to raise specificity.

Include common user variations of trigger terms ("Python style", "type annotations", "idiomatic Python") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Python domain and subtopics ("Pythonic 惯用法、PEP 8 标准、类型提示") but lists topic areas rather than concrete actions like extract/fill/merge, so it is not comprehensive.

2 / 3

Completeness

It states what the skill covers but never says when Claude should use it; the missing "Use when…" clause caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Relevant domain terms (Python, PEP 8, Pythonic, type hints) are present, but there is no "Use when…" phrasing and common user variations are not covered.

2 / 3

Distinctiveness Conflict Risk

The Python focus is a clear niche, but "最佳实践" (best practices) is broad and lacks distinct explicit triggers, so it could still overlap with general coding skills.

2 / 3

Total

8

/

12

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 (751 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.