python-async-patterns
Python asyncio patterns for concurrent programming. Triggers on: asyncio, async, await, coroutine, gather, semaphore, TaskGroup, event loop, aiohttp, concurrent.
88
86%
Does it follow best practices?
Impact
91%
1.71xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
72%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 excels at trigger term coverage and distinctiveness, providing a comprehensive list of asyncio-related keywords that would reliably match user queries. However, it falls short on specificity of capabilities—it says 'patterns' without describing what concrete actions or outputs the skill provides (e.g., writing async code, debugging event loops, implementing concurrency patterns). Adding concrete actions would significantly improve it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Implements async/await coroutines, manages concurrent tasks with gather and TaskGroup, handles rate limiting with semaphores, and integrates with aiohttp for async HTTP requests.'
Rephrase the trigger list into a more natural 'Use when...' clause, e.g., 'Use when the user asks about asyncio, async/await syntax, coroutines, event loops, or concurrent Python programming.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python asyncio / concurrent programming) but does not list specific concrete actions like 'create coroutines', 'manage task groups', or 'implement semaphore-based rate limiting'. It mentions patterns but doesn't describe what it actually does. | 2 / 3 |
Completeness | The 'what' is partially addressed ('Python asyncio patterns for concurrent programming') but lacks detail on specific actions. The 'when' is addressed via 'Triggers on:' which serves as an explicit trigger clause, but the what is too thin to earn a 3. The trigger list partially compensates for the missing 'Use when...' clause. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would use: asyncio, async, await, coroutine, gather, semaphore, TaskGroup, event loop, aiohttp, concurrent. These are the exact keywords a developer would mention when needing help with async Python. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in Python asyncio/async programming. The specific trigger terms like 'asyncio', 'coroutine', 'TaskGroup', 'aiohttp' are unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that is concise, actionable, and well-organized. It covers the essential asyncio patterns with executable code, highlights critical pitfalls with concrete wrong/right examples, and appropriately delegates detailed topics to reference files. The structure respects Claude's intelligence while providing genuinely useful, non-obvious guidance like the orphaned task warning and blocking call detection.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and pattern-focused. No unnecessary explanations of what asyncio is or how Python works. The code examples are minimal but complete, and the quick reference table is efficiently structured. | 3 / 3 |
Actionability | All patterns include executable Python code that can be directly used. The critical warnings section provides concrete wrong/right comparisons with specific code, and the quick reference table maps patterns to use cases clearly. | 3 / 3 |
Workflow Clarity | For a reference/patterns skill, the workflow is appropriately structured: core concepts first, then progressively more advanced patterns, then warnings about common mistakes. This is not a multi-step destructive operation, so validation checkpoints aren't required. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in the main file and clearly signaled one-level-deep references to detailed patterns (concurrency, aiohttp, sync-async mixing, debugging, production, error handling, performance). Related skills and prerequisites are also well-linked. | 3 / 3 |
Total | 12 / 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
- NeverSight/skills_feed
- Commit
9f4534c
- 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.