CtrlK
BlogDocsLog inGet started
Tessl Logo

python-patterns

Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.

49

Quality

54%

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/AI-Agents-Safe-Coding-Skills-claude/skills/python-patterns/SKILL.md

The canonical home for this skill is python-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 body is a well-organized reference of decision trees and tables that assumes some intelligence but over-explains basic Python concepts and offers mostly heuristic rather than executable guidance. With no bundle files, the single 440-line document leaves progressive disclosure underdeveloped.

Suggestions

Move detailed reference material (framework comparison tables, async library selection, Django/FastAPI principles) into separate files under references/ and link to them one level deep from SKILL.md.

Replace or supplement ASCII decision trees with concrete, copy-paste-ready code snippets for the most common cases (e.g., a minimal async FastAPI endpoint, a Celery task).

Trim explanations of basic concepts Claude already knows (Optional/Union semantics, what Pydantic is) to keep the body lean.

DimensionReasoningScore

Conciseness

The ASCII decision trees and tables are token-efficient, but sections explain basics Claude already knows ("Optional → might be None", "Union → one of multiple types") and repeat motivational lines. Mostly efficient but could be tightened, so it sits at 3 rather than 4.

3 / 5

Actionability

Guidance is largely heuristic decision trees and comparison tables rather than copy-paste executable code; the few code blocks (type hints, FastAPI/Pydantic, async test) are minimal. It is above 2 because concrete selection tables exist, but below 4 because most direction is not directly executable.

3 / 5

Workflow Clarity

A decision checklist (section 10) and "How to Use" steps provide a rough sequence, but there is no multi-step workflow with explicit validation checkpoints. It is an advisory skill so the destructive/batch cap does not apply, leaving it at 3.

3 / 5

Progressive Disclosure

The ~440-line body is well divided into 11 numbered sections, but all content is inlined in SKILL.md with no bundle files or one-level-deep references; content that could live in separate reference files (framework comparison, async library table, Django/FastAPI sections) is inline. The under-50-line simple-skill exception does not apply, so it stays at 3.

3 / 5

Total

12

/

20

Passed

Description

58%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 clearly conveys what the skill covers but omits any explicit trigger/"Use when" guidance, which caps completeness and limits trigger-term quality. It is specific and reasonably distinctive within the Python domain.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., choosing a Python framework, deciding async vs sync, structuring a Python project).

Include common user-facing synonyms and concrete triggers (e.g., "FastAPI vs Django", "type hints", "async/await") to improve trigger-term coverage.

Tighten "Teaches thinking, not copying." into the trigger clause so the when-to-use is concrete rather than philosophical.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete areas ("Framework selection, async patterns, type hints, project structure"), with only minor coverage gaps. It falls below 5 because these are topic areas rather than fully enumerated concrete actions.

4 / 5

Completeness

It clearly states the "what" (Python development principles and decision-making across listed areas) but provides no explicit "when" guidance; per the rubric a missing "Use when..." clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "framework selection", "async patterns", and "type hints" appear, but there is no "Use when..." trigger phrase and common synonyms/variations users would naturally say are missing. Not a 4 because the keyword set is incomplete and lacks explicit trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

The Python architecture/decision-making niche is mostly distinct from other skills with only minor overlap risk against general coding skills. Not a 5 because "Python development" is still fairly broad.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.