python
Python development guidelines and best practices. Use when working with Python code.
62
52%
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 ./skills/python/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.
This description is too vague and generic to effectively guide skill selection. While it correctly uses third person voice and includes a 'Use when' clause, it fails to specify what concrete actions the skill enables and would likely conflict with any other Python-related skills in a multi-skill environment.
Suggestions
Replace 'guidelines and best practices' with specific concrete actions (e.g., 'Enforces PEP 8 formatting, adds type hints, structures modules, configures linting tools').
Narrow the 'Use when' clause to specific triggers that distinguish this from other Python skills (e.g., 'Use when setting up a new Python project, configuring code style, or asking about Python conventions').
Add more trigger term variations like '.py files', 'Python style', 'PEP 8', 'code formatting', 'project structure' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'guidelines and best practices' without listing any concrete actions. It doesn't specify what actions Claude will perform (e.g., formatting, linting, type hints, testing). | 1 / 3 |
Completeness | Has a weak 'what' (guidelines and best practices) and includes a 'Use when' clause, but the 'when' is overly broad ('working with Python code') and the 'what' lacks specificity about actual capabilities. | 2 / 3 |
Trigger Term Quality | Includes 'Python' and 'Python code' which are natural terms users would say, but misses common variations like '.py files', 'scripts', 'modules', 'packages', or specific Python concepts. | 2 / 3 |
Distinctiveness Conflict Risk | 'Working with Python code' is extremely broad and would conflict with any Python-related skill (testing, debugging, refactoring, documentation, etc.). No clear niche is established. | 1 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured Python guidelines skill that efficiently communicates standards without over-explaining. Its main weakness is the lack of concrete code examples to illustrate patterns like Protocol-based dependency injection, Pydantic model usage, and test structure. The guidelines are clear but would be more actionable with executable snippets.
Suggestions
Add a concrete code example showing Protocol-based dependency injection pattern
Include a Pydantic v2 model example demonstrating preferred validation and serialization patterns
Add a brief test example showing the AAA pattern and naming conventions in practice
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic Python concepts Claude already knows. Every section provides specific, actionable guidance without padding or unnecessary context. | 3 / 3 |
Actionability | Provides clear guidelines and patterns but lacks executable code examples. Instructions like 'Use Pydantic v2' and 'Use Protocol classes' are specific but would benefit from concrete code snippets showing the preferred patterns. | 2 / 3 |
Workflow Clarity | The Implementation section provides a basic workflow (type check, test, commit) but lacks explicit validation checkpoints or feedback loops. Testing section has clear structure but no step-by-step process for test-driven development. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and appropriate references to external files (uv-scripts.md, uv-monorepo.md) for specialized topics. Content is appropriately scoped for a SKILL.md overview without being monolithic. | 3 / 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
- siviter-xyz/dot-agent
- Commit
3376255
- 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.