CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-anti-patterns

Use this skill when reviewing Python code for common 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

78%

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

Quality

Content

75%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, highly actionable anti-patterns reference: consistent BAD/GOOD code pairs, named tools and fixes, and a usable review checklist. The content is efficient and easy to navigate; the only notable flaws are a redundant fixes table that repeats inline content and code fragments that assume undefined context names.

DimensionReasoningScore

Conciseness

The body is lean: every anti-pattern is a compact BAD/GOOD code pair with one-line fixes and zero explanation of concepts Claude already knows. The trimmable redundancy is the 'Common Fixes Summary' table, which restates fixes already shown (and the checklist re-lists the section titles), but it is compact — minor instances that could be trimmed, fitting anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Every item pairs a concrete BAD example with an executable GOOD fix naming specific tools (pydantic_settings, httpx.AsyncClient, pytest.raises, context managers). Minor gaps: fragments rely on undefined names (url, User, BatchResult, client) and a '...' placeholder, so guidance is mostly executable but not copy-paste ready — anchor 4, not 5.

4 / 5

Workflow Clarity

As a single-task reference skill its action is unambiguous: 'Review this before finalizing implementations' plus a 14-item 'Quick Review Checklist' to verify against. It is a read-only review checklist, so the destructive/batch validation cap does not apply. What keeps it below 5 is the absence of any sequence or priority for applying the checks (e.g., which categories to scan first).

4 / 5

Progressive Disclosure

No bundle files exist; the skill is one self-contained file with clear category sections (Infrastructure, Architecture, Error Handling, Resource, Type Safety, Testing), a checklist, and a summary table — easy to navigate with no nested references. At ~350 lines it exceeds the under-50-line simple-skill case, and some deep-dive examples could be offloaded to a references/ file, so it fits 'good structure with minor organization gaps' rather than a 5.

4 / 5

Total

16

/

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, multi-trigger 'Use when' clause and natural keywords for the Python code-review niche. Its main weakness is specificity: it says 'common anti-patterns' without naming any, leaving the what circular and slightly increasing overlap with general code-review skills.

Suggestions

Name 2-3 concrete coverage areas in the description (e.g., 'Detects bare excepts, blocking calls in async code, missing type hints, and untested error paths') to raise specificity and distinctiveness.

Add common trigger variations users say, such as 'code review', 'best practices', or 'code smells', to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('reviewing Python code for common anti-patterns') and 1-2 actions (review, use as a checklist) but never specifies which anti-patterns it covers, matching the anchor for domain plus 1-2 concrete actions without comprehensive coverage. It does not list several specific actions, so it falls below anchor 4.

3 / 5

Completeness

Both parts are explicit: the 'what' ('a checklist of common anti-patterns to avoid' implied by 'reviewing Python code for common anti-patterns... Use as a checklist') and a concrete 'when' clause ('when reviewing code, before finalizing implementations, or when debugging issues'). The 'what' is somewhat circular ('anti-patterns to avoid' without naming any), keeping it below the fully concrete anchor 5.

4 / 5

Trigger Term Quality

Natural phrases users would say are present: 'reviewing Python code', 'anti-patterns', 'checklist', 'reviewing code', 'debugging issues', 'bad practices'. A few common terms are missing ('code review', 'best practices', 'lint', 'code smells'), which fits good coverage with a few gaps rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear Python anti-patterns niche with mostly distinct triggers, but the broad phrase 'reviewing code' and 'finalizing implementations' could overlap with generic code-review or linting skills. Minor overlap risk with closely related skills matches anchor 4 rather than the minimal-conflict anchor 5.

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

wshobson/agents

Path

plugins/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.