python-async-patterns
Python asyncio patterns for concurrent programming. Triggers on: asyncio, async, await, coroutine, gather, semaphore, TaskGroup, event loop, aiohttp, concurrent.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill python-async-patterns83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description has strong trigger term coverage and clear distinctiveness for Python asyncio work. However, it lacks specific concrete actions (what patterns does it teach?) and doesn't include an explicit 'Use when...' clause to guide skill selection. The description reads more like a keyword list than a complete skill description.
Suggestions
Add specific concrete actions like 'Implements async/await patterns, manages concurrent tasks with gather and TaskGroup, handles rate limiting with semaphores, structures event loops'
Add an explicit 'Use when...' clause such as 'Use when the user needs help with Python async programming, concurrent HTTP requests, or managing multiple coroutines'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python asyncio) and mentions 'concurrent programming' as the general action, but doesn't list specific concrete actions like 'create coroutines', 'manage task groups', or 'handle async HTTP requests'. | 2 / 3 |
Completeness | The 'what' is partially addressed (asyncio patterns for concurrent programming), and while 'Triggers on:' provides keywords, it lacks an explicit 'Use when...' clause explaining the scenarios when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'asyncio', 'async', 'await', 'coroutine', 'gather', 'semaphore', 'TaskGroup', 'event loop', 'aiohttp', 'concurrent' - these are all terms developers naturally use when working with async Python. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with Python asyncio-specific terminology. The trigger terms like 'asyncio', 'coroutine', 'TaskGroup', 'aiohttp' are highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%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-crafted skill that excels at conciseness and actionability, providing lean, executable async patterns without unnecessary explanation. The progressive disclosure is excellent with clear navigation to advanced topics. The main weakness is workflow clarity - while individual patterns are clear, there's no guidance on debugging async issues or validating that async code is working correctly.
Suggestions
Add a brief troubleshooting workflow: how to identify blocking calls, verify concurrency is working, and debug common async issues (e.g., 'Run with PYTHONASYNCIODEBUG=1 to detect unawaited coroutines')
Consider adding a decision tree or brief guidance on pattern selection (e.g., 'Use TaskGroup when tasks should fail together, gather when you want partial results')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what asyncio is or how Python works. Every code block demonstrates a specific pattern without preamble. The skill assumes Claude understands async concepts and jumps straight to executable examples. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. Patterns include complete function signatures, proper imports, and real-world usage. The 'Critical Warnings' section provides concrete WRONG vs CORRECT comparisons that are immediately actionable. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no guidance on when to choose one pattern over another in a workflow, and no validation steps for debugging async issues. The patterns are presented as isolated snippets rather than a coherent workflow for building async applications. | 2 / 3 |
Progressive Disclosure | Excellent structure with core concepts upfront, followed by numbered patterns, a quick reference table, and clearly signaled one-level-deep references to detailed materials. The 'Additional Resources' section properly points to specific reference files for advanced topics. | 3 / 3 |
Total | 11 / 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 | |
- 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.