CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

modern-python-development

Provides modern Python 3.12+ best practices covering syntax, type hints, error handling, project structure, and idiomatic patterns. Use when the user asks to "write Python code", "create a Python module", "set up a Python project", "review Python code", "refactor Python", "add type hints", "fix Python style", or when generating any Python source code. Does not cover any specific library or framework — see the fastmcp, chromadb, pytest-best-practices and fastapi-best-practices skills for those.

70

Quality

88%

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

78%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 reference skill: lean tables and executable examples, clean section organization, and exemplary one-level-deep progressive disclosure to four real reference files. Weakest spots are a recitation of basic PEP 8 naming rules and a couple of code placeholders that keep examples from being fully copy-paste ready.

Suggestions

Trim or relocate the standard PEP 8 naming-convention table (module, class, function, variable, constant rows) into a reference file, keeping only the modern/non-obvious rows (type alias statement, dunder/mangling notes) inline.

Replace placeholder bodies like 'def calculate_total(items: list[float], *, tax_rate: float = 0.0) -> float: ...' with complete runnable examples, and show the imports needed for snippets like 'type Handler[**P] = Callable[P, Awaitable[None]]'.

Add brief decision guidance for interacting dataclass options (when to prefer frozen vs. slots vs. kw_only) so the rules can be applied without ambiguity when they combine.

DimensionReasoningScore

Conciseness

The body is dominated by dense tables and short code blocks, and the legacy-to-modern table is pure value-add Claude benefits from having. Not 5 because the Naming Conventions table recites standard PEP 8 knowledge Claude already has; not 3 since that is the only clearly trimmable section.

4 / 5

Actionability

Concrete, executable snippets throughout (frozen/slots dataclass, 'except* ValidationError as eg', walrus operator, match/case) plus specific rules. Minor gaps keep it below anchor 5: 'def calculate_total(...) -> float: ...' uses a placeholder body, and 'type Handler[**P] = Callable[P, Awaitable[None]]' omits the imports needed to run.

4 / 5

Workflow Clarity

A reference skill with no multi-step process and no destructive or batch operations, so no validation cap applies, and each rule's application is unambiguous. Held at 4 rather than 5 because there is no prioritization or decision guidance when rules interact (e.g., choosing between frozen, slots, and kw_only dataclass options).

4 / 5

Progressive Disclosure

The body is a genuine overview with detail pushed to four real reference files (references/modern-syntax.md, type-hints.md, patterns.md, project-structure.md, all verified present). Each link is clearly signaled with a one-line content summary, references are exactly one level deep, and navigation is easy — matches the anchor-5 example.

5 / 5

Total

17

/

20

Passed

Description

95%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: it states a clear scope, enumerates concrete coverage areas, provides eight natural trigger phrases, and explicitly fences off library-specific skills by name. Only minor improvements are possible (naming concrete actions rather than topic areas, mentioning .py files).

DimensionReasoningScore

Specificity

Names the domain and lists five specific coverage areas ('syntax, type hints, error handling, project structure, and idiomatic patterns'), which is several specific capabilities. Falls short of anchor 5 because these are topic areas rather than concrete actions, and ahead of anchor 3 because coverage spans more than 1-2 items.

4 / 5

Completeness

Explicitly answers both what ('modern Python 3.12+ best practices covering syntax, type hints, error handling, project structure, and idiomatic patterns') and when (a 'Use when' clause with eight concrete trigger phrases). This matches the anchor-5 example structure exactly; not 4 because the 'when' is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Eight natural phrases users would actually say: 'write Python code', 'create a Python module', 'set up a Python project', 'review Python code', 'refactor Python', 'add type hints', 'fix Python style', plus the catch-all 'generating any Python source code'. Coverage is comprehensive with synonyms; only nit is no '.py' extension mention, which does not drop it to anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (stdlib-only Python 3.12+) with explicit de-scoping: 'Does not cover any specific library or framework — see the fastmcp, chromadb, pytest-best-practices and fastapi-best-practices skills for those'. Named sibling skills and boundary guidance keep conflict risk minimal even though 'any Python source code' is a broad trigger.

5 / 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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

provectus/awos-recruitment

Path

registry/skills/modern-python-development/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.