async-python-patterns
Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems.
55
Quality
45%
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/async-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 the technical domain (async Python/asyncio) but reads more like a course catalog entry than actionable skill guidance. It lacks concrete actions, explicit trigger conditions, and natural user language. The absence of a 'Use when...' clause significantly weakens its utility for skill selection.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about asyncio, coroutines, event loops, async/await syntax, or making Python code non-blocking'.
Replace abstract language ('comprehensive guidance', 'high-performance systems') with concrete actions like 'Write async functions, manage event loops, handle concurrent tasks, implement async context managers'.
Include natural user phrases and variations: 'async Python', 'coroutines', 'aiohttp', 'run tasks concurrently', 'await', 'event loop'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (async Python, asyncio, concurrent programming) and mentions some concepts (async/await, non-blocking systems), but doesn't list concrete actions like 'write async functions', 'handle coroutines', or 'implement task queues'. | 2 / 3 |
Completeness | Describes what the skill covers (async Python guidance) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, and the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'asyncio', 'async/await', 'asynchronous', but misses common user variations like 'coroutines', 'event loop', 'aiohttp', 'concurrent.futures', or phrases users might say like 'make my code async' or 'parallel execution'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to async Python/asyncio which narrows the scope, but 'concurrent programming patterns' and 'high-performance systems' are broad enough to potentially overlap with threading, multiprocessing, or general performance optimization skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, serving effectively as a routing document to detailed resources. However, it severely lacks actionability - there are no code examples, specific patterns, or executable guidance in the main skill file itself. Users must rely entirely on the referenced playbook for any concrete implementation details.
Suggestions
Add at least one minimal executable code example showing a basic async pattern (e.g., asyncio.gather with multiple coroutines)
Include a concrete example of timeout and error handling pattern rather than just mentioning 'add timeouts'
Add a quick validation step or debugging tip directly in the skill (e.g., 'Use asyncio.run() for entry point, check for unawaited coroutine warnings')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding explanations of what asyncio is or how async/await works. Every section serves a purpose without padding or unnecessary context that Claude would already know. | 3 / 3 |
Actionability | The skill provides only abstract guidance ('pick concurrency patterns', 'add timeouts') with no concrete code examples, specific commands, or executable snippets. It describes what to do rather than showing how to do it. | 1 / 3 |
Workflow Clarity | The Instructions section lists steps in a logical sequence, but lacks explicit validation checkpoints or feedback loops. For async code which can have subtle bugs, missing debugging/validation steps is a gap. | 2 / 3 |
Progressive Disclosure | The skill appropriately serves as an overview with clear, one-level-deep references to the implementation playbook. Navigation is well-signaled and content is appropriately split between overview and detailed resource. | 3 / 3 |
Total | 9 / 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- 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.