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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

50%

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

The skill body is well-structured and lean, with a clear use/do-not-use framing and a logical instruction sequence, but it stops at mid-level on every dimension: it offers no executable code, lacks explicit validation checkpoints, repeats the playbook reference, and—most consequentially—points to a detailed examples file that is missing from the bundle.

Suggestions

Either add the missing `resources/implementation-playbook.md` (with the promised detailed patterns/examples) or remove the dangling references to it so navigation is not a dead end.

Include at least one small executable async snippet (e.g. an `asyncio.gather` with `asyncio.wait_for` timeout and cancellation) to lift actionability from abstract guidance to copy-paste-ready code.

Add an explicit validation/feedback step in the workflow, such as "run the async tests; if a task hangs or is cancelled unexpectedly, tighten the timeout and re-run," to give the sequence a concrete checkpoint.

De-duplicate the playbook reference (mention it once in Resources) and drop the verbatim restatement of the description from the opening line to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but it could be tightened: the opening sentence restates the description verbatim, and the reference to `resources/implementation-playbook.md` appears three times (Instructions, a standalone line, and Resources). It is above score 1 (no padded concept explanations) but below score 3 because of this repetition.	2 / 3
Actionability	The instructions name concrete patterns ("tasks, gather, queues, pools," "timeouts, backpressure, structured error handling") rather than pure abstraction, but provide no executable code or commands, and the deferred "detailed examples" live in `resources/implementation-playbook.md`, which is absent from the bundle. It is not score 1 (concrete named guidance exists) and not score 3 (no copy-paste-ready code and the example source is missing).	2 / 3
Workflow Clarity	The Instructions form a clear sequence (clarify workload → pick patterns → add timeouts/error handling → include testing/debugging → open playbook if needed) with a "stop and ask" checkpoint in Limitations. However, there is no explicit validate-then-fix feedback loop for the async work itself, so checkpoints are mostly implicit. It is above score 1 (sequence is present and ordered) but below score 3 (no concrete validation/verification steps).	2 / 3
Progressive Disclosure	The body is well-organized into clearly labeled sections (Use when, Do not use when, Instructions, Resources, Limitations) and signals a one-level-deep reference to `resources/implementation-playbook.md`. However, that referenced file does not exist in the bundle (no resources/, references/, scripts/, or assets/ directories), so navigation to the detailed material is a dead end. It is above score 1 (good structure, no deep nesting) but below score 3 because the single external reference is broken.	2 / 3
	Total	8 / 12 Passed

Description

50%

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 establishes a clear async-Python niche and what the skill covers, but it omits any explicit "Use when..." trigger guidance and relies on somewhat abstract, jargon-heavy language. This caps completeness and trigger-term quality, leaving every dimension at the mid-level anchor.

Suggestions

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

Replace abstract verbs ("implementing," "building") with concrete capabilities users would request, such as "orchestrate concurrent tasks with asyncio.gather, add timeouts and cancellation, manage backpressure."

Include natural user phrasings ("async Python," "asyncio tasks," "event loop") to broaden trigger coverage beyond technical jargon.

Dimension	Reasoning	Score
Specificity	The description names a clear domain ("asynchronous Python applications using asyncio, concurrent programming patterns, and async/await") with action verbs ("implementing," "building"), but the actions remain abstract rather than a list of concrete capabilities. It is not score 1 because it is far from vague like "Helps with documents," and not score 3 because it lacks multiple specific concrete actions analogous to "extract text, fill forms, merge documents."	2 / 3
Completeness	The description clearly answers "what" (comprehensive async Python guidance) but provides no "Use when..." clause or equivalent explicit trigger guidance for "when." Per the rubric guideline, a missing explicit trigger caps completeness at 2, and it is not score 1 because the "what" is explicit and substantive.	2 / 3
Trigger Term Quality	It surfaces some natural developer terms ("asyncio," "async/await," "asynchronous Python") a user might say, but leans jargon-heavy ("concurrent programming patterns," "non-blocking systems") and misses common variations. It is above score 1 (which has no natural keywords) but below score 3, which expects broad coverage of the phrasings users actually use.	2 / 3
Distinctiveness Conflict Risk	The async-Python/asyncio niche is somewhat specific and distinguishable, but the broad "concurrent programming patterns" framing and absence of explicit triggers mean it could still overlap with general Python or concurrency skills. It is not score 1 (not generic like "Helps with code and documents") and not score 3 (no distinct, unambiguous triggers that prevent misfiring).	2 / 3
	Total	8 / 12 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: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 days 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.