Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
53
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/python-patterns/SKILL.mdQuality
Discovery
32%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 identifies a clear domain (Python development) and lists relevant topic areas, but lacks concrete action verbs and explicit trigger conditions. The tagline 'Teaches thinking, not copying' is stylistic but doesn't help Claude determine when to use this skill. Without a 'Use when...' clause, Claude may struggle to select this skill appropriately from a large skill library.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks about Python architecture decisions, choosing between frameworks, or structuring a new Python project'
Convert topic nouns into action verbs: 'Guides framework selection decisions, explains async/await patterns, recommends type hint strategies' instead of just listing categories
Add common user phrasings as triggers: 'FastAPI vs Flask', 'should I use asyncio', 'Python project layout', 'mypy', 'pydantic'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python development) and lists several specific areas (framework selection, async patterns, type hints, project structure), but these are categories rather than concrete actions. No verbs describing what the skill actually does. | 2 / 3 |
Completeness | Describes what topics it covers but has no explicit 'Use when...' clause or trigger guidance. The phrase 'Teaches thinking, not copying' hints at approach but doesn't tell Claude when to select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Python', 'async patterns', 'type hints', 'framework selection' that users might mention, but missing common variations like 'Python best practices', 'code organization', 'FastAPI vs Django', or 'typing'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Python development principles' is fairly broad and could overlap with general Python coding skills. The specific mentions of framework selection and async patterns add some distinction, but 'project structure' and 'type hints' are common to many Python skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid conceptual framework for Python development decisions with useful decision trees and comparison tables. However, it leans too heavily on abstract guidance rather than executable examples, and the emphasis on 'thinking not copying' results in a lack of concrete, actionable code. The content would benefit from more copy-paste ready examples and better progressive disclosure through external references.
Suggestions
Add executable code examples for each framework showing a minimal working endpoint (not just type hint patterns)
Split detailed framework-specific guidance (Django ORM patterns, FastAPI dependency injection examples) into separate reference files
Include a concrete validation workflow for framework selection decisions (e.g., 'After choosing, verify by checking: X, Y, Z')
Remove explanations of concepts Claude already knows (e.g., what I/O-bound vs CPU-bound means) to improve token efficiency
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient with decision trees and tables, but includes some unnecessary explanation (e.g., explaining what async is good for when Claude knows this). The 'Remember' callout and some repetitive guidance could be trimmed. | 2 / 3 |
Actionability | Provides decision frameworks and comparison tables which are useful, but lacks executable code examples. The few code snippets shown are incomplete patterns rather than copy-paste ready implementations. Most guidance is conceptual rather than concrete. | 2 / 3 |
Workflow Clarity | The decision checklist at the end provides a workflow, but individual sections lack clear step-by-step sequences. No validation checkpoints or feedback loops for the decision-making process. The decision trees are helpful but don't guide through actual implementation steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document with no references to external files for detailed topics. Advanced topics like Celery workflows or Django ORM patterns could be split into separate reference files. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
7114206
Table of Contents
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.