python-pro
Use when building Python 3.11+ applications requiring type safety, async programming, or production-grade patterns. Invoke for type hints, pytest, async/await, dataclasses, mypy configuration.
72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has strong trigger term coverage and completeness with explicit 'Use when' and 'Invoke for' clauses. However, it lacks concrete action verbs describing what the skill actually does (e.g., 'generates', 'configures', 'validates') and relies on somewhat abstract concepts like 'production-grade patterns' that reduce distinctiveness.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Generates type-annotated Python code, configures mypy, writes pytest test suites'
Replace vague 'production-grade patterns' with specific patterns like 'error handling, logging configuration, dependency injection'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python 3.11+) and mentions several features (type hints, pytest, async/await, dataclasses, mypy), but describes requirements/patterns rather than concrete actions the skill performs. Missing action verbs like 'creates', 'configures', 'validates'. | 2 / 3 |
Completeness | Explicitly answers both what ('building Python 3.11+ applications requiring type safety, async programming, or production-grade patterns') and when ('Use when...', 'Invoke for...'). Has clear trigger guidance with specific invocation scenarios. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'type hints', 'pytest', 'async/await', 'dataclasses', 'mypy', 'type safety', 'async programming'. These are terms developers naturally use when seeking Python help. | 3 / 3 |
Distinctiveness Conflict Risk | While Python 3.11+ and specific features like mypy/dataclasses add some distinction, 'production-grade patterns' is vague and could overlap with general Python or software engineering skills. The async/pytest mentions could conflict with testing or concurrency skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has strong structural organization with excellent progressive disclosure through its reference table, but lacks the concrete, executable examples that would make it truly actionable. The constraints are well-defined but the workflow needs explicit validation checkpoints, and the content could be more concise by removing sections that explain Claude's role rather than providing actionable guidance.
Suggestions
Add concrete code examples showing type-hinted functions, dataclass usage, and pytest fixtures rather than just describing what to provide
Enhance the workflow with explicit validation checkpoints (e.g., 'If mypy fails: fix type errors and re-run before proceeding')
Remove or condense the 'Role Definition' section - Claude doesn't need to be told it's a senior engineer
Include a minimal mypy configuration example (pyproject.toml snippet) since mypy strict mode is referenced multiple times
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the 'Role Definition' section explaining what a senior Python engineer does, and the 'Related Skills' section which adds little value. The reference table and constraints are well-organized but could be tighter. | 2 / 3 |
Actionability | The skill provides good high-level guidance with clear constraints (MUST DO/MUST NOT DO) but lacks concrete, executable code examples. The 'Output Templates' section describes what to provide but doesn't show actual examples of type-hinted code, pytest fixtures, or mypy configuration. | 2 / 3 |
Workflow Clarity | The 5-step core workflow is clearly sequenced but lacks validation checkpoints and feedback loops. Step 5 mentions running mypy/black/ruff but doesn't specify what to do if validation fails or how to iterate on errors. | 2 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear topics, file paths, and 'Load When' conditions. The skill serves as a concise overview pointing to detailed materials in one-level-deep references, making navigation easy. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.