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.

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/async-python-patterns/SKILL.md

Quality

Content

43%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized into clear sections, but it stays at a high directive level with no executable code, no validation checkpoints, and a reference to a playbook file that is missing from the bundle, weakening both actionability and progressive disclosure.

Suggestions

Provide at least one executable snippet (e.g. asyncio.gather with timeout/cancellation, or an asyncio.Queue producer/consumer) so the guidance is copy-paste ready instead of abstract.

Add an explicit validation checkpoint in the workflow — e.g. 'run with asyncio debug mode and confirm no unhandled task exceptions before shipping' — to satisfy the feedback-loop expectation for async batch/background work.

Either create `resources/implementation-playbook.md` and the `resources/` directory so the reference resolves, or remove the three dangling references and inline the key patterns.

Dimension	Reasoning	Score
Conciseness	The body is lean — bulleted directives that assume Claude's knowledge with no padding or concept explanation — but the same `resources/implementation-playbook.md` reference appears three times (Instructions line, a standalone refer line, and the Resources section), a minor trimmable redundancy that keeps it from 5.	4 / 5
Actionability	Guidance is high-level ('Pick concurrency patterns (tasks, gather, queues, pools) with cancellation rules', 'Add timeouts, backpressure') with no executable code or commands, and the one concrete escalation ('open resources/implementation-playbook.md') points to a file that does not exist.	2 / 5
Workflow Clarity	A rough sequence exists (clarify → pick patterns → add timeouts/handling → include testing) but steps are abstract directives with no validation checkpoints, and async background/queue work — flagged as in scope — has no verify/fix/retry feedback loop.	2 / 5
Progressive Disclosure	Structure and signaling are good (clearly sectioned body pointing one level deep to a detailed file), but the referenced `resources/implementation-playbook.md` is absent — no resources directory or bundle file exists — so the disclosure chain is broken rather than navigable.	3 / 5
	Total	11 / 20 Passed

Description

56%Weight 40%Scale 1-5

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 clearly scopes the skill to async Python and uses natural trigger terms, but it relies on generic action verbs and omits an explicit 'Use when' trigger, leaving completeness capped and specificity below midpoint.

Suggestions

Replace generic verbs ('implementing', 'building') with concrete actions such as 'orchestrates concurrent tasks with asyncio.gather', 'applies timeouts and cancellation to coroutines', and 'queues I/O work with backpressure'.

Add an explicit trigger clause, e.g. 'Use when building async/await services, concurrent I/O pipelines, or non-blocking APIs with asyncio'.

Include a couple of natural synonyms like 'coroutines', 'event loop', and 'tasks' to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (async Python, asyncio, concurrent patterns, async/await) but the only actions are generic verbs ('implementing', 'building') with no concrete discrete capabilities, matching the 'Names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	A clear 'what' is present (guidance for implementing async Python systems) but there is no 'Use when...' clause or equivalent explicit trigger, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural developer vocabulary — 'asynchronous Python', 'asyncio', 'concurrent programming', 'async/await', 'non-blocking' — that users would actually say; a few common variants like 'coroutines' or 'event loop' are missing, so it falls short of 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to async/concurrent Python with distinct triggers and minimal conflict risk versus sync Python or other-language skills; only minor overlap with general concurrency skills keeps it from 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/async-python-patterns/SKILL.md
Commit: 1f67c44

Reviewed: about 17 hours ago

Table of Contents

Discovery Implementation Validation

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.