python-best-practices
Provides Python patterns for type-first development with dataclasses, discriminated unions, NewType, and Protocol. Must use when reading or writing Python files.
83
Quality
78%
Does it follow best practices?
Impact
88%
1.66xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/python-best-practices/SKILL.mdQuality
Discovery
77%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 excels at specifying concrete capabilities with precise Python typing constructs and includes an explicit 'when' clause. However, the trigger condition 'reading or writing Python files' is too broad, causing potential conflicts with other Python skills, and the trigger terms could include more natural user language around typing and type hints.
Suggestions
Narrow the trigger condition to typing-specific scenarios: 'Use when adding type hints, defining data models, or when user mentions typing, type safety, or dataclasses'
Add natural trigger terms users would say: 'type hints', 'type annotations', 'typed Python', 'mypy', 'type checking'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete patterns: 'dataclasses, discriminated unions, NewType, and Protocol' - these are precise, actionable Python typing constructs. | 3 / 3 |
Completeness | Clearly answers what ('Provides Python patterns for type-first development with dataclasses, discriminated unions, NewType, and Protocol') and when ('Must use when reading or writing Python files') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Python files' and technical terms like 'dataclasses', 'Protocol', but missing common user phrases like 'type hints', 'typing', '.py files', or 'type annotations' that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The trigger 'reading or writing Python files' is overly broad and would conflict with any Python-related skill. The typing-specific content is distinctive, but the trigger condition makes it fire for all Python work. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent code examples that demonstrate Python type-first patterns effectively. The content is concise and assumes Claude's competence. Minor improvements could include adding validation checkpoints to the workflow and potentially splitting some detailed sections into separate reference files for better progressive disclosure.
Suggestions
Add explicit validation/verification steps to the type-first workflow (e.g., 'Run type checker after step 2 to verify signatures')
Consider splitting the ty tool section and configuration examples into separate reference files, keeping SKILL.md as a focused overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting patterns through executable code examples without explaining basic Python concepts Claude already knows. Every section earns its place with actionable patterns. | 3 / 3 |
Actionability | All code examples are complete and executable, from dataclass definitions to discriminated unions to config loading. The patterns are copy-paste ready with clear, specific implementations. | 3 / 3 |
Workflow Clarity | The type-first development workflow lists 4 steps but lacks explicit validation checkpoints or feedback loops. For a patterns/best-practices skill, the sequence is present but could benefit from clearer verification steps when applying these patterns. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~200 lines) that could benefit from splitting detailed examples (like the ty tool section or configuration patterns) into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
5342bca
- 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.