Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.
90
88%
Does it follow best practices?
Impact
91%
1.46xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
92%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 is a strong description that clearly articulates specific capabilities and includes explicit trigger guidance with both 'Use when' and 'Invoke for' clauses. It contains rich, natural trigger terms that Python developers would use. The main weakness is its broad scope spanning type safety, async programming, testing, and linting, which could overlap with more focused skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generates type-annotated code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, validates code with black and ruff, and covers dataclasses, dependency injection, logging configuration, and structured error handling. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates type-annotated Python code, configures mypy, writes pytest suites, validates with black/ruff) and 'when' with explicit triggers ('Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling' and 'Invoke for type hints, async/await patterns, dataclasses...'). | 3 / 3 |
Trigger Term Quality | Includes many natural keywords users would say: 'Python 3.11+', 'type hints', 'async/await', 'dataclasses', 'pytest', 'mypy', 'black', 'ruff', 'dependency injection', 'logging', 'error handling', 'type safety'. These are terms developers naturally use when requesting Python development help. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies Python 3.11+ with type safety and async focus, the scope is quite broad covering general Python development patterns. It could overlap with a general Python coding skill, a testing skill, or a linting/formatting skill. The combination of concerns (type safety + async + testing + linting) makes it somewhat distinctive but also sprawling. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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 skill with excellent actionability through complete code examples, clear workflow with validation feedback loops, and good progressive disclosure via the reference table. Its main weakness is moderate verbosity—some sections restate things Claude already knows (mutable defaults, bare excepts, PEP 8 basics) and the Knowledge Reference line at the end adds no value. Trimming these redundancies would make it more token-efficient.
Suggestions
Remove or significantly trim the MUST NOT DO items that Claude already knows (mutable default arguments, bare except clauses, PEP 8 compliance) to improve token efficiency.
Remove the 'Knowledge Reference' keyword list at the bottom—it provides no actionable guidance and wastes tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The 'When to Use This Skill' section largely restates the description, the MUST DO/MUST NOT DO lists contain items Claude already knows (e.g., 'don't use mutable default arguments', 'don't use bare except'), and the 'Knowledge Reference' section at the bottom is a redundant keyword list. However, the code examples are lean and the reference table is well-structured. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready code examples covering type-annotated functions, dataclasses with validation, async patterns, pytest fixtures with parametrize, and mypy configuration. Each example is complete and runnable, with specific commands for validation tools. | 3 / 3 |
Workflow Clarity | The Core Workflow section provides a clear 5-step sequence with explicit validation checkpoints and feedback loops: mypy failures trigger fix-and-rerun, test failures trigger debug-and-iterate, and ruff/black issues trigger auto-fix-and-revalidate. The mypy section also explicitly states errors must be resolved before implementation is considered complete. | 3 / 3 |
Progressive Disclosure | The reference table elegantly provides one-level-deep progressive disclosure with clear 'Load When' guidance for each topic. The main skill serves as a well-organized overview with code examples for common patterns, while detailed guidance for specific topics is appropriately deferred to reference files. | 3 / 3 |
Total | 11 / 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.
3d95bb1
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.