Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
68
Quality
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/async-python-patterns/SKILL.mdQuality
Discovery
89%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 well-structured description with explicit 'Use when' guidance and good trigger term coverage for async Python development. The main weakness is the somewhat vague capability description - 'Master' is aspirational rather than action-oriented, and specific operations (event loops, coroutines, async generators) are not enumerated.
Suggestions
Replace 'Master' with specific concrete actions like 'Implement coroutines, manage event loops, handle async context managers, and coordinate concurrent tasks'
Add more specific file/pattern triggers like '.py files with async def', 'aiohttp', 'asyncio.gather'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python asyncio, concurrent programming) and mentions some actions (building async APIs, concurrent systems), but lacks specific concrete actions like 'implement coroutines', 'manage event loops', or 'handle async context managers'. | 2 / 3 |
Completeness | Clearly answers both what ('Master Python asyncio, concurrent programming, and async/await patterns') and when ('Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'asyncio', 'async/await', 'concurrent', 'async APIs', 'I/O-bound', 'non-blocking'. These are terms developers naturally use when seeking help with async Python. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Python async programming with distinct triggers like 'asyncio', 'async/await', 'non-blocking'. Unlikely to conflict with general Python skills or other language concurrency skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a routing document to the implementation playbook rather than providing standalone value. While it has good progressive disclosure structure, it lacks any actionable code examples or concrete guidance, making it nearly useless without accessing the referenced resource. The 'when to use' sections add bulk without adding value Claude doesn't already possess.
Suggestions
Add at least one minimal, executable async/await code example (e.g., basic asyncio.gather pattern) directly in the skill body
Replace the vague instruction bullets with concrete guidance, such as specific timeout values, backpressure thresholds, or decision criteria for choosing between asyncio.gather vs TaskGroup
Remove or significantly condense the 'Use this skill when' and 'Do not use this skill when' sections - Claude already knows when async patterns are appropriate
Add a validation checkpoint in the workflow, such as 'Verify event loop compatibility before implementing' with a concrete check
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary sections like 'Use this skill when' and 'Do not use this skill when' lists that explain obvious use cases Claude would already understand. The actual instructions are lean but the surrounding context adds padding. | 2 / 3 |
Actionability | The skill provides no concrete code examples, commands, or executable guidance. It only offers vague directives like 'Pick concurrency patterns' and 'Add timeouts' without showing how to implement any of these. All actual implementation is deferred to a referenced file. | 1 / 3 |
Workflow Clarity | The instructions section provides a rough sequence of steps (clarify, pick patterns, add handling, include testing), but lacks validation checkpoints, concrete decision criteria, or feedback loops for error recovery. The workflow is implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | The skill appropriately structures content as an overview with clear, one-level-deep references to the implementation playbook. Navigation is well-signaled with explicit file paths in both the instructions and resources sections. | 3 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
3395991
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.