CtrlK
BlogDocsLog inGet started
Tessl Logo

async-python-patterns

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.

66

Quality

62%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/async-python-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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'

DimensionReasoningScore

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

35%

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 table of contents pointing to an external playbook rather than providing actionable guidance itself. It lacks any concrete code examples, specific patterns, or executable instructions - everything substantive is deferred to the referenced resource file. The 'when to use' sections add bulk without value since Claude understands async use cases.

Suggestions

Add at least one concrete, executable async code example (e.g., basic asyncio.gather pattern or async context manager) directly in the skill body

Remove or significantly condense the 'Use this skill when' and 'Do not use this skill when' sections - Claude understands these contexts

Transform the abstract instructions ('Pick concurrency patterns', 'Add timeouts') into specific, actionable guidance with code snippets

Include a minimal quick-start section that provides immediate value without requiring navigation to the external resource

DimensionReasoningScore

Conciseness

The skill is relatively brief but includes some unnecessary sections like 'Use this skill when' and 'Do not use this skill when' which explain obvious context Claude would understand. The instructions themselves are lean but the framing adds bulk.

2 / 3

Actionability

No concrete code examples, commands, or executable guidance provided. The instructions are abstract directives ('Pick concurrency patterns', 'Add timeouts') without showing how to implement them. Everything actionable is deferred to an external file.

1 / 3

Workflow Clarity

Steps are listed in a logical sequence (clarify -> pick patterns -> add handling -> include testing), but they lack specificity and validation checkpoints. No concrete workflow for implementing async patterns is provided.

2 / 3

Progressive Disclosure

References to external resource file are present and one-level deep, but the main skill content is too thin - it's essentially just a pointer to another file with minimal standalone value. The overview doesn't provide enough quick-start content.

2 / 3

Total

7

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
duclm1x1/Dive-Ai
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.