python-best-practices

Pythonic code with modern type hints, dataclasses, async patterns, packaging, and testing

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/python-best-practices/SKILL.md

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and token-efficient with executable examples and no concept over-explanation; its only real weakness is that everything is packed into a single monolithic file with no progressive disclosure into reference files.

Suggestions

Split the larger reference blocks (full pyproject.toml config, the testing section, the async patterns) into files under references/ and signal them from SKILL.md so the main file stays a lean overview.

Add a short 'Quick start' or 'Quick reference' section at the top pointing to each detailed section/reference for faster navigation.

Move the version-anchored syntax notes (3.12+/3.10+) into a dedicated 'Version-specific syntax' reference so the main body stays version-agnostic and avoids time-sensitive clutter.

Dimension	Reasoning	Score
Conciseness	The body is lean: each section pairs a tight code block with a one-line rule and never explains concepts Claude already knows (no 'what is a dataclass' padding), so every token earns its place per the top anchor.	3 / 3
Actionability	Guidance is fully executable throughout — runnable type-hint snippets, a copy-paste pyproject.toml, concrete commands ('uv venv', 'mypy --strict', 'ruff'), and complete pytest fixtures — matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	This is a reference/style skill rather than a multi-step process; per the simple-skills scoring note, clearly organized single-purpose content can score 3, and there are no destructive/batch operations that would demand validation feedback loops.	3 / 3
Progressive Disclosure	No bundle files exist and the entire ~280-line reference lives inline in SKILL.md; the self-contained pyproject.toml, testing, and async sections could plausibly be split into references, matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	11 / 12 Passed

Description

50%

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 lists relevant Python domains but reads as topic enumeration rather than action-oriented capability statements, and it lacks an explicit 'Use when...' trigger clause that the rubric requires for full completeness.

Suggestions

Rewrite as concrete actions, e.g. 'Apply Pythonic patterns: add modern type hints, build dataclasses/Pydantic models, write async HTTP code, scaffold pyproject.toml packaging, and structure pytest tests.'

Add an explicit trigger clause: 'Use when writing or reviewing Python 3.12+ code, scaffolding a project, or when the user mentions type hints, dataclasses, async, packaging, or testing.'

Include common user phrasings/variants (e.g. 'type hints', 'typing', 'async/await', 'pyproject', 'pytest') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Enumerates concrete topics ('type hints, dataclasses, async patterns, packaging, and testing') but these are domains/topics rather than the concrete actions ('extract', 'fill', 'merge') the top anchor rewards, so it sits at 'names domain and some actions' rather than the comprehensive action-listing level.	2 / 3
Completeness	It clearly states what the skill covers but has no 'Use when...' trigger clause, and the guideline explicitly caps completeness at 2 when such explicit trigger guidance is missing.	2 / 3
Trigger Term Quality	Terms like 'type hints', 'dataclasses', 'async', 'packaging', and 'testing' are ones a user might say, but coverage is a flat topic list without common variations or the natural phrasing users employ when requesting these, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	'Python best practices' is a recognizable niche narrowed by its topic list, but the breadth ('code', 'packaging', 'testing') means it could still overlap with general coding-skills, matching 'somewhat specific but could still overlap'.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: rohitg00/awesome-claude-code-toolkit
Path: skills/python-best-practices/SKILL.md
Commit: ebdf1d5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.