python-async-patterns

Python asyncio patterns for concurrent programming. Triggers on: asyncio, async, await, coroutine, gather, semaphore, TaskGroup, event loop, aiohttp, concurrent.

1.71x

Quality

—

Does it follow best practices?

Impact

91%

1.71x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

A lean, well-organized async pattern catalog with high-value pitfall warnings, undermined by non-copy-paste-ready examples (undefined helpers, missing imports) and a set of referenced bundle files that do not exist on disk.

Suggestions

Create the referenced bundle files (./references/*.md, ./scripts/find-blocking-calls.sh, ./assets/async-project-template.py) or remove the dangling references so progressive disclosure points to real detail.

Make code examples self-contained: add missing imports (aiohttp, time, requests) and define or stub the helper functions (fetch_one, process_one, slow_operation, create_connection) so snippets are copy-paste executable.

Either add a short validation/checklist step for the risky patterns (e.g., verify no blocking calls via find-blocking-calls.sh) or explicitly frame the skill as a reference catalog so workflow clarity expectations are clear.

Dimension	Reasoning	Score
Conciseness	The body is code-first with terse, high-value annotations ("# WRONG - blocks event loop", "# May be garbage collected!") and no explanation of basic concepts Claude already knows, matching the lean anchor 3 despite minor repetition of the aiohttp session pattern.	3 / 3
Actionability	Examples use real asyncio APIs (gather, Semaphore, TaskGroup, timeout) but reference undefined helpers (fetch_one, process_one, slow_operation, create_connection) and omit imports (aiohttp), so they are illustrative rather than copy-paste executable, matching anchor 2 rather than the fully-runnable anchor 3.	2 / 3
Workflow Clarity	The content is a well-organized pattern catalog (numbered patterns, WRONG/CORRECT warnings, quick-reference table) but contains no multi-step workflow with explicit validation checkpoints, so it sits at anchor 2 rather than the sequenced-with-validation anchor 3.	2 / 3
Progressive Disclosure	The "Additional Resources" section clearly signals one-level-deep references with per-file descriptions, but none of the 7 referenced reference files, the scan script, or the asset actually exist, so the disclosure is broken in practice and detail content is effectively all inline, capping the score at anchor 2.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit, natural trigger terms and a clear asyncio niche. Its main weakness is a topic-level what-statement that names the domain but does not enumerate concrete actions.

Dimension	Reasoning	Score
Specificity	Quotes "Python asyncio patterns for concurrent programming" name the domain clearly but list no concrete actions the skill performs, matching anchor 2 rather than the multi-action anchor 3, while being more specific than vague anchor-1 examples like "Helps with documents".	2 / 3
Completeness	Both elements are present: a what-statement ("asyncio patterns for concurrent programming") and an explicit "Triggers on:" clause equivalent to a "Use when" trigger, so the missing-trigger cap at 2 does not apply; the what is topic-level rather than action-rich but both are explicitly stated.	3 / 3
Trigger Term Quality	The explicit "Triggers on: asyncio, async, await, coroutine, gather, semaphore, TaskGroup, event loop, aiohttp, concurrent" gives good coverage of natural terms a developer would actually say, matching the anchor-3 example.	3 / 3
Distinctiveness Conflict Risk	The asyncio concurrency niche with distinct triggers (gather, semaphore, TaskGroup, event loop) is unlikely to fire for unrelated skills, matching the clear-niche anchor 3.	3 / 3
	Total	11 / 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: NeverSight/skills_feed
Commit: 26d37ce

Reviewed: 4 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.