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 has strong trigger term coverage and clear distinctiveness for Python asyncio programming. However, it lacks specific concrete actions (what exactly does it help with beyond 'patterns'?) and would benefit from an explicit 'Use when...' clause rather than just a trigger term list. The description is functional but could be more informative about the actual capabilities provided.
Suggestions
Add specific concrete actions like 'Implements async/await coroutines, manages concurrent tasks with gather and TaskGroup, handles rate limiting with semaphores, configures event loops'.
Replace 'Triggers on:' with a 'Use when...' clause, e.g., 'Use when the user needs help writing async Python code, managing concurrent tasks, or working with asyncio patterns including coroutines, task groups, and aiohttp.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python asyncio/concurrent programming) and implies patterns, but doesn't list specific concrete actions like 'create coroutines, manage task groups, implement semaphore-based rate limiting'. The word 'patterns' is somewhat vague. | 2 / 3 |
Completeness | The 'what' is partially addressed (asyncio patterns for concurrent programming) and trigger terms are listed, but there's no explicit 'Use when...' clause explaining when Claude should select this skill. The 'Triggers on:' list partially compensates but doesn't fully replace an explicit 'when' guidance. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: asyncio, async, await, coroutine, gather, semaphore, TaskGroup, event loop, aiohttp, concurrent. These are the exact keywords a developer would use when seeking help with async Python. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in Python asyncio/concurrent programming. The specific trigger terms like asyncio, coroutine, TaskGroup, aiohttp, and event loop 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 provides executable code patterns for the most common asyncio use cases while deferring detailed topics to clearly labeled reference files. The critical warnings section adds significant value by showing concrete anti-patterns alongside correct alternatives.
| 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 patterns cover real use cases like bounded concurrency and timeouts. | 3 / 3 |
Workflow Clarity | For a reference/patterns skill, the workflow is clear: core concepts first, then progressively more advanced patterns, then warnings about common mistakes. The critical warnings section serves as validation guidance, showing exactly what to avoid and why. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file and well-signaled one-level-deep references to seven specific topic files. The references are clearly labeled with descriptive summaries, plus scripts and assets are appropriately separated. | 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
f772de4
- 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.