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.

56

Quality

64%

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

Quality

Content

63%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-structured, actionable decision-making reference with concrete trees, tables, and code, but it is a monolithic single file that inlines material a progressive-disclosure design would split into referenced files, and time-sensitive version markers are not isolated in a deprecated section.

Suggestions

Move time-sensitive specifics (2025, Django 5.0+, Pydantic v2) into a clearly labeled 'Current versions' or 'Deprecated/old patterns' section so they don't penalize conciseness.

Split deep framework-specific guidance (Django, FastAPI) into separate referenced files (e.g. DJANGO.md, FASTAPI.md) with one-level-deep links from SKILL.md to improve progressive disclosure.

De-duplicate the Decision Checklist and Anti-Patterns sections, which restate the framework/async decision trees already covered above, to tighten conciseness.

DimensionReasoningScore

Conciseness

Content is mostly efficient dense reference material (decision trees, tables) rather than prose padding, but time-sensitive markers ("for 2025", "Django 5.0+", "Pydantic v2") appear inline rather than in a deprecated/old-patterns section, and several sections (checklist, anti-patterns) restate the decision trees, so it lands at the midpoint rather than 4.

3 / 5

Actionability

Provides concrete decision trees, comparison tables, specific library recommendations (httpx, asyncpg, SQLAlchemy 2.0 async), and executable code patterns for type hints, FastAPI DI, and async testing, with only minor gaps where examples are illustrative rather than copy-paste ready.

4 / 5

Workflow Clarity

The 'Decision Checklist' section sequences the pre-implementation decision process with explicit checkboxes and the decision trees act as branching workflows; minor gaps only, and no destructive/batch operations require validation feedback loops.

4 / 5

Progressive Disclosure

Section structure is clear with good headers, but all content (~300 lines) is inlined in SKILL.md with no bundle files or signaled one-level-deep references, so framework/Django/FastAPI detail that could live in separate files remains inline.

3 / 5

Total

14

/

20

Passed

Description

66%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 is specific and well-scoped to Python decision-making with good natural trigger terms, but it omits any explicit "Use when..." trigger guidance, which caps completeness and leaves the activation context implicit.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building Python applications, choosing frameworks, or deciding async vs sync architecture.'

Include common synonyms or file/keyword triggers (e.g. 'FastAPI', 'Django', 'asyncio', 'Pydantic') to broaden natural keyword coverage.

Reframe sub-areas as concrete actions where possible (e.g. 'Select frameworks', 'Structure projects') to push specificity toward 5.

DimensionReasoningScore

Specificity

Lists several concrete sub-areas ("Framework selection, async patterns, type hints, project structure") rather than vague abstractions, though they are topics rather than fully concrete actions, placing it just below the comprehensive 5 anchor.

4 / 5

Completeness

Has a clear "what" ("Python development principles and decision-making" plus sub-areas) but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("async patterns", "type hints", "project structure", "framework selection") with good coverage, missing only some synonyms and explicit trigger phrasing.

4 / 5

Distinctiveness Conflict Risk

Scoped to Python development decision-making with specific sub-domains, making it mostly distinct from non-Python skills; only minor overlap risk with broad general Python skills.

4 / 5

Total

15

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
MODSetter/SurfSense
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.