CtrlK
BlogDocsLog inGet started
Tessl Logo

python-async-patterns

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

85

1.71x
Quality

81%

Does it follow best practices?

Impact

91%

1.71x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 a concise, mostly executable pattern catalog with good quick-reference navigation and useful wrong-vs-correct warnings. Its main gaps are undefined helper functions in examples, no explicit validation/feedback loops for batch async operations, and references to bundle files that are not present.

Suggestions

Define or import the placeholder helpers used in examples (fetch_one, process_one, slow_operation, create_connection) and include the aiohttp import so snippets are copy-paste runnable.

Add a short validation/checklist step for batch patterns (e.g., check gather's return_exceptions results for failures before proceeding) to establish a feedback loop.

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

DimensionReasoningScore

Conciseness

The body is lean: short headers, executable code blocks, and inline comments that add value without explaining basic concepts Claude already knows; every section earns its tokens.

5 / 5

Actionability

Multiple concrete, executable patterns (gather, Semaphore, TaskGroup, timeout, asynccontextmanager) cover common cases, but several examples rely on undefined helpers (fetch_one, process_one, slow_operation, create_connection) and omit imports, leaving minor gaps from copy-paste readiness.

4 / 5

Workflow Clarity

This is a patterns catalog rather than a sequenced workflow, and batch patterns like gather appear without validation/verification checkpoints; the wrong-vs-correct warnings help but do not provide explicit feedback loops, capping this at 3 per the batch-operations guidance.

3 / 5

Progressive Disclosure

The body is well structured with a clearly signaled, one-level-deep 'Additional Resources' section, but the referenced bundle files (./references/*.md, ./scripts/*.sh, ./assets/*.py) do not exist on disk, so the navigation the structure promises is broken when scored against the actual bundle.

3 / 5

Total

15

/

20

Passed

Description

90%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 is well-constructed with an explicit trigger clause and comprehensive, natural keywords that clearly carve out the Python asyncio niche. Its only weakness is that the 'what' statement is generic and does not enumerate concrete capabilities beyond the trigger list.

DimensionReasoningScore

Specificity

The 'what' ('Python asyncio patterns for concurrent programming') names the domain but describes only generic actions; concrete capabilities like gather, TaskGroup, and timeout appear only as trigger terms rather than stated actions, so it sits between anchor 2 and 3, closer to 3 for hinting at 1-2 concrete actions.

3 / 5

Completeness

It explicitly answers both 'what' (asyncio patterns for concurrent programming) and 'when' (an explicit 'Triggers on:' clause with concrete trigger phrases), matching the anchor for a clear and explicit what+when.

5 / 5

Trigger Term Quality

'Triggers on: asyncio, async, await, coroutine, gather, semaphore, TaskGroup, event loop, aiohttp, concurrent' gives comprehensive coverage of the natural terms a user would say when needing async help, including API-level synonyms.

5 / 5

Distinctiveness Conflict Risk

The Python asyncio niche is clear and the triggers are specific to async concurrency, giving a distinct profile with minimal overlap risk against unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NeverSight/skills_feed
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.