CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-design-patterns

Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I/O and business logic.

Quality

83%

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

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.

Well-structured skill with exemplary progressive disclosure — a lean overview tier pointing to a real, one-level-deep reference — and mostly actionable guidance. Its weaknesses are redundant re-teaching of well-known principles across Core Concepts and Best Practices, and the absence of an explicit sequenced decision workflow.

Suggestions

Collapse the Core Concepts definitions and the overlapping Best Practices items into one section: state the pattern names and their one-line application rule once, removing the duplicate restatements of KISS, single responsibility, composition, and rule of three.

Add a short explicit decision procedure (e.g., 'When deciding whether to abstract: 1) count the instances, 2) check whether copies are diverging dangerously, 3) apply the rule of three, 4) prefer composition for the extracted variation') so the guidance has a sequenced flow rather than only concept-by-concept sections.

Make the Quick Start example self-contained (define Formatter/JsonFormatter or use built-ins) so the contrast between over-engineered and simple is copy-paste verifiable.

DimensionReasoningScore

Conciseness

The Core Concepts section restates well-known principles Claude already knows ("Choose the simplest solution that works", "Each unit should have one reason to change"), and the Best Practices Summary re-covers four of the five core concepts (keep it simple, single responsibility, compose don't inherit, rule of three) — mostly efficient but with unnecessary explanation and tightening opportunities, not the minor-trim case at 4.

3 / 5

Actionability

Concrete guidance is present: a real dict-lookup code example contrasting over-engineering, and specific directives like "Keep the composition shallow (2-3 levels)" and "keeping the dependency arrow pointing downward (API → Service → Repository)". Minor gaps: the Quick Start snippet references undefined types (Formatter, JsonFormatter) and is not copy-paste runnable, and the body offers only one code example.

4 / 5

Workflow Clarity

There is no explicit sequenced decision procedure — the usage flow (when-to-use → concepts → quick start → details → troubleshooting) is implicit in section ordering, and troubleshooting entries give problem→action pairs without an ordered procedure or checkpoints. Not below 3 since the guidance itself is coherent and non-destructive, but not 4 because no clear step sequence is articulated.

3 / 5

Progressive Disclosure

The body is a genuine overview tier with one well-signaled, one-level-deep reference ("Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.") — the reference exists, contains 353 lines of real worked examples, and contains no nested references, matching the clear-overview anchor exactly.

5 / 5

Total

15

/

20

Passed

Description

96%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.

A strong description: explicit what-and-when structure with rich, natural trigger phrases and synonym coverage. Its only weakness is minor overlap risk with sibling Python architecture/testing skills on layering and testability triggers.

DimensionReasoningScore

Specificity

The description names concrete patterns ("KISS, Separation of Concerns, Single Responsibility, and composition over inheritance") and enumerates multiple specific usage actions ("refactoring a God class or monolithic function", "evaluating a pull request for structural issues like tight coupling or leaking internal types", "choosing between inheritance and composition"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers both "what" ("Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance") and "when" ("Use this skill when..." followed by six concrete trigger scenarios), exactly the anchor-5 pattern.

5 / 5

Trigger Term Quality

It covers natural developer phrases with synonyms ("God class or monolithic function", "add a new abstraction or live with duplication", "tight coupling", "hard to test because of entangled I/O and business logic") — the kind of wording users actually say, matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

The niche (structural design decisions) is clear, but triggers like "designing a new service... choosing how to layer responsibilities" and "a codebase is becoming hard to test" overlap with closely related skills (python-testing-patterns, python-project-structure are linked as siblings), fitting "mostly distinct; minor overlap risk with closely related skills" rather than the minimal-conflict anchor at 5.

4 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

wshobson/agents

Path

plugins/python-development/skills/python-design-patterns/SKILL.md

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.