CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-anti-patterns

Common Python anti-patterns to avoid. Use as a checklist when reviewing code, before finalizing implementations, or when debugging issues that might stem from known bad practices.

Quality

75%

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 ./tests/ext_conformance/artifacts/agents-wshobson/python-development/skills/python-anti-patterns/SKILL.md

The canonical home for this skill is python-anti-patterns in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured reference checklist with consistent BAD/GOOD code examples, a clear usage section, and an actionable final checklist — as a simple single-purpose skill its workflow is unambiguous. The main costs are token efficiency (basic-pattern entries and a redundant summary table duplicate the checklist) and the monolithic 350-line layout with no progressive disclosure into reference files.

Suggestions

Cut or compress entries that re-teach fundamentals Claude already knows (bare except, unclosed resources, missing type hints) down to one-line checklist items, keeping full BAD/GOOD examples only for the less-obvious patterns (double retry, partial failures, blocking in async).

Remove the 'Common Fixes Summary' table or merge it with the 'Quick Review Checklist' — the two sections repeat nearly the same content.

Split the detailed per-pattern examples into one-level-deep reference files (e.g., references/architecture.md, references/error-handling.md) and keep SKILL.md as the overview plus the quick checklist.

DimensionReasoningScore

Conciseness

The BAD/GOOD paired-example format is lean overall, but several entries teach fundamentals Claude already knows (bare except handling, context managers for file closing, type hints), and the 'Common Fixes Summary' table largely duplicates the 'Quick Review Checklist' section. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than anchor 4, where only minor trimming would be needed.

3 / 5

Actionability

Every anti-pattern gets concrete code on both the bad and fixed sides plus an actionable final checklist, so guidance is mostly executable. Minor gaps keep it below anchor 5: snippets reference undefined variables (`url`, `db`), and 'Untyped Collections'/'Over-Mocking' use `...` stubs or bare Mock lists without a complete example.

4 / 5

Workflow Clarity

This is a simple single-purpose skill and the single action — review code against the checklist — is unambiguous, with an explicit 'When to Use This Skill' section, per-pattern fixes, and a final 'Quick Review Checklist'. No destructive or batch operations are involved, so the validation cap does not apply.

5 / 5

Progressive Disclosure

Section headers are clear and well-organized, but the skill is ~350 lines fully inline with zero reference files. The 13 patterns with BAD/GOOD example pairs are content that could be split into one-level-deep references (e.g., per-category), matching anchor 3 ('some structure but content that should be separate is inline'). The under-50-line exception for scoring 5 clearly does not apply.

3 / 5

Total

15

/

20

Passed

Description

70%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 solid description with an explicit 'Use as a checklist when...' trigger clause covering three concrete scenarios, and clear Python-specific niche framing. Its main weakness is that the 'what' side stays generic — it never hints at the categories of anti-patterns covered (error handling, resources, types, testing, etc.), which limits specificity and distinctiveness from adjacent review skills.

Suggestions

Enumerate the anti-pattern categories in the description (e.g., 'error handling, resource management, async, typing, and testing anti-patterns') to raise specificity without adding length.

Add natural trigger synonyms users actually say, such as 'code review', 'code smells', or 'Python best practices', to improve trigger coverage.

Sharpen the trigger to distinguish this skill from general code-review skills, e.g., 'Use when reviewing Python code for known bad practices rather than correctness bugs.'

DimensionReasoningScore

Specificity

The description names the domain ("Common Python anti-patterns to avoid") and one concrete artifact ("checklist"), but the named actions ("reviewing code", "debugging issues") are usage scenarios rather than enumerated capabilities of the skill — matching anchor 3's 'domain and 1-2 concrete actions, not comprehensive' rather than anchor 4's list of several specific actions.

3 / 5

Completeness

Both what ("Common Python anti-patterns to avoid" as a checklist) and when ("Use as a checklist when reviewing code, before finalizing implementations, or when debugging") are explicitly present with a proper 'Use when' clause. Not a 5 because the 'what' is a general category without any enumeration of the anti-pattern areas covered.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "Python", "anti-patterns", "reviewing code", "debugging", "known bad practices". It falls short of anchor 5 because common variations like "code smells", "code review", or "best practices" are absent.

4 / 5

Distinctiveness Conflict Risk

"Python anti-patterns" is a clear niche with mostly distinct triggers, but the trigger phrases "reviewing code" and "debugging issues" could overlap with a general code-review or debugging skill — anchor 4's 'minor overlap risk with closely related skills'.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Dicklesworthstone/pi_agent_rust

Path

tests/ext_conformance/artifacts/agents-wshobson/python-development/skills/python-anti-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.