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.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

50%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 clean, well-organized overview with useful use/don't-use lists, but it stops at high-level directives with no executable examples and relies on a referenced playbook file that is not actually bundled. Several redundancies (intro restatement, triple reference to the same file) reduce token efficiency.

Suggestions

Add a small, concrete async code snippet (e.g., asyncio.gather with timeout/cancellation) directly in SKILL.md so the skill is actionable without the external file.

Remove the duplicate reference — keep only the Resources-section pointer to `resources/implementation-playbook.md` and delete the standalone 'Refer to ...' line and the inline Instructions reference.

Provide the referenced `resources/implementation-playbook.md` bundle file (or remove the reference) so progressive disclosure resolves to real content.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with tight bullet sections, but the opening sentence restates the frontmatter description and `resources/implementation-playbook.md` is referenced three times (Instructions bullet, a standalone line, and the Resources section), which is redundant padding that could be tightened.	3 / 5
Actionability	Instructions name concrete concepts (tasks, gather, queues, pools, timeouts, backpressure, cancellation rules) but give only high-level directives ('Pick concurrency patterns', 'Add timeouts') with no concrete code, commands, or specific steps — the actual executable detail is deferred to an external file.	3 / 5
Workflow Clarity	A logical sequence is implied (clarify workload → pick patterns → add timeouts/backpressure/errors → include testing), but these read as considerations rather than operational steps and there are no validation checkpoints or error-recovery feedback loops.	3 / 5
Progressive Disclosure	Structure is well-organized with clear sections and a clearly signaled one-level reference, but the referenced `resources/implementation-playbook.md` does not exist in the bundle (no resources/, references/, scripts/, or assets/ directory is present), making the progressive-disclosure promise a dangling pointer with no detailed material actually delivered.	3 / 5
	Total	12 / 20 Passed

Description

73%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.

A well-structured description that clearly answers both what and when with concrete, natural trigger phrases. Its main weakness is specificity: 'Master ... patterns' is a generic action verb and the rest lists application contexts rather than concrete capabilities.

Suggestions

Replace the generic verb 'Master ... patterns' with one or two concrete capabilities (e.g., 'Implement async tasks, gather/queue concurrency, and cancellation patterns').

Add commonly used synonyms such as 'event loop', 'coroutines', or 'asynchronous' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Python asyncio, concurrent programming, and async/await patterns') but the only action verb is the generic 'Master ... patterns' alongside context phrases like 'building async APIs', which describe usage contexts rather than concrete skill actions.	2 / 5
Completeness	It explicitly states both what ('Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications') and when ('Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage — 'async APIs', 'concurrent systems', 'I/O-bound applications', 'non-blocking operations', 'asyncio', 'async/await' — but it omits common synonyms a user might say such as 'event loop', 'coroutines', 'concurrency', or 'asynchronous'.	4 / 5
Distinctiveness Conflict Risk	The async-Python niche is mostly distinct with clear async-specific triggers, though 'concurrent systems' and 'I/O-bound applications' carry minor overlap risk with a general Python or concurrency skill.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/async-python-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.