CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/async-python-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

This skill is essentially a thin table of contents with no substantive content of its own. It defers all actionable guidance to referenced files that aren't provided, leaving the SKILL.md itself without any executable code, concrete examples, or specific patterns. The structure shows intent for progressive disclosure but is undermined by inconsistent paths and the complete absence of inline actionable content.

Suggestions

Add at least 2-3 concrete, executable asyncio code examples directly in the SKILL.md (e.g., basic async/await pattern, asyncio.gather for concurrent I/O, a simple queue pattern) so the skill is useful even without the referenced files.

Replace vague instructions like 'Pick concurrency patterns' and 'Add timeouts, backpressure' with specific guidance showing when to use each pattern and how (e.g., 'Use asyncio.gather() for independent I/O tasks; use asyncio.Queue for producer-consumer with backpressure via maxsize=N').

Fix the inconsistent file references — `resources/implementation-playbook.md` and `./sub-skills/implementation-playbook.md` appear to reference different paths for the same content. Consolidate to a single, correct path.

Remove the introductory paragraph that restates the title and trim the 'Use this skill when' list to the most non-obvious scenarios to improve conciseness.

DimensionReasoningScore

Conciseness

The 'Use this skill when' and 'Do not use this skill when' sections are somewhat verbose and list obvious scenarios Claude could infer. The instructions section is reasonably lean but the overall content has padding that doesn't add much value (e.g., the introductory paragraph restates the title).

2 / 3

Actionability

The skill provides no concrete code, no executable examples, no specific commands, and no copy-paste ready patterns. The instructions are abstract directives like 'Pick concurrency patterns' and 'Add timeouts, backpressure' without showing how. All actionable content is deferred to a referenced file that isn't provided.

1 / 3

Workflow Clarity

The instructions section provides a rough sequence (clarify → pick patterns → add error handling → test), but steps are vague with no validation checkpoints, no feedback loops, and no concrete verification steps. For async programming which can involve subtle bugs, the lack of debugging/validation specifics is a gap.

2 / 3

Progressive Disclosure

The skill references `resources/implementation-playbook.md` and a sub-skill, which is good structure in principle. However, no bundle files are provided, the reference appears twice redundantly (Resources section and Knowledge Modules section with a different path), and the paths are inconsistent (`resources/implementation-playbook.md` vs `./sub-skills/implementation-playbook.md`), creating confusion about where the actual content lives.

2 / 3

Total

7

/

12

Passed

Description

89%

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

This is a solid description with explicit 'Use when' guidance and good trigger term coverage for Python async programming. Its main weakness is that the capability description leans toward abstract mastery language ('Master Python asyncio') rather than listing specific concrete actions the skill enables. The word 'Master' also reads slightly like instructional framing rather than a capability description.

Suggestions

Replace 'Master Python asyncio...' with specific concrete actions like 'Implements Python asyncio event loops, manages coroutines, creates task groups, and applies async/await patterns'.

Add file extension or framework triggers like '.py', 'aiohttp', 'FastAPI async', 'asyncpg' to improve trigger term coverage for common async Python use cases.

DimensionReasoningScore

Specificity

Names the domain (Python asyncio, concurrent programming) and some general actions ('building async APIs, concurrent systems'), but doesn't list multiple specific concrete actions like 'create event loops, manage coroutines, implement task groups, handle async context managers'.

2 / 3

Completeness

Clearly answers both what ('Master Python asyncio, concurrent programming, and async/await patterns') and when ('Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations') with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say: 'asyncio', 'async/await', 'concurrent', 'async APIs', 'I/O-bound', 'non-blocking'. These are terms developers naturally use when seeking help with Python async programming.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to Python asyncio and async/await patterns specifically, which is a distinct niche unlikely to conflict with general Python skills or other language-specific concurrency skills. The trigger terms are specific enough to avoid false matches.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.