Name: python-pro
Rating: 44 (1 reviews)
Author: administrakt0r

python-pro

Master Python 3.12+ with modern features, async programming, performance optimization, and production-ready practices. Expert in the latest Python ecosystem including uv, ruff, pydantic, and FastAPI.

Quality

45%

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

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

Quality

Content

35%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 functions as a persona declaration rather than an actionable skill: it lists capabilities and concepts Claude already knows while providing no code, commands, or concrete procedures. It needs executable examples, a tighter core, and externalized reference material to become genuinely useful.

Suggestions

Replace the padded capability and knowledge-base lists with a lean core plus a few copy-paste-ready snippets (e.g., a uv project init, a ruff/pyproject config, a minimal FastAPI route with Pydantic validation).

Add explicit validation checkpoints to the workflow (e.g., 'Run ruff check and mypy; only proceed when both pass') so the four-step sequence has feedback loops.

Move the detailed ecosystem/tooling reference material into separate files under references/ and link to them one level deep, keeping SKILL.md as an overview.

Dimension	Reasoning	Score
Conciseness	The body is a long enumeration of concepts Claude already knows (context managers and the with statement, itertools, Singleton/Factory/Observer, SOLID principles), padding the context with restated knowledge rather than novel guidance.	2 / 5
Actionability	There is no executable code or concrete command anywhere in the body — only high-level hints like 'Confirm runtime, dependencies, and performance targets' and 'Choose patterns (async, typing, tooling)', which lack the specific steps to execute.	2 / 5
Workflow Clarity	A four-step sequence is present (confirm → choose patterns → implement and test → profile and tune) but it carries no validation checkpoints or feedback loops, fitting the 'steps listed but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	Section headers give the body some structure, but all the capability and knowledge-base reference material is inlined in SKILL.md with no bundle files or one-level-deep references, so navigation and content splitting are only partially realized.	3 / 5
	Total	10 / 20 Passed

Description

56%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 scopes the modern-Python niche and surfaces several natural trigger terms, but it leans on generic capability verbs and omits any 'Use when…' trigger guidance. Rewriting in third person with concrete actions and an explicit trigger clause would lift it above the midpoint.

Suggestions

Add an explicit 'Use when…' clause naming concrete trigger situations (e.g., 'Use when writing or reviewing Python 3.12+ code, setting up uv/ruff, or building FastAPI services').

Replace generic verbs ('Master', 'Expert in') with third-person concrete actions ('Writes, reviews, and optimizes Python 3.12+ code…') to satisfy the voice rule and boost specificity.

Include common synonyms users say ('Python', 'py', 'type hints', 'pytest', 'asyncio') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The verbs are generic ('Master Python 3.12+', 'Expert in the latest Python ecosystem') — they name a domain and tooling rather than concrete actions like extracting or filling. The imperative 'Master…' reads as implicit second person, which reduces specificity by one per the voice guideline, landing at the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It has a clear 'what' (modern Python features, async, performance, ecosystem tooling) but no 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 3.	3 / 5
Trigger Term Quality	It surfaces natural terms users actually say — 'Python 3.12+', 'async programming', 'uv', 'ruff', 'pydantic', 'FastAPI' — giving good keyword coverage, though common synonyms like 'Python', 'py', 'type hints', or 'pytest' are absent.	4 / 5
Distinctiveness Conflict Risk	The modern-Python niche with named tools (uv, ruff, pydantic, FastAPI) is mostly distinct from sibling skills, with only minor overlap risk against general coding skills.	4 / 5
	Total	13 / 20 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
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
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/python-pro/SKILL.md
Commit: 57c135b

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.