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.

52

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./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.

The body is well-organized into clear sections and reasonably concise, but it offers only abstract directives with no executable guidance and points to a resource file that is missing from the bundle. The triple-repeated broken reference undermines both actionability and navigation.

Suggestions

Add at least one executable example (e.g. an asyncio.gather snippet with timeout and cancellation) instead of only directing Claude to "add timeouts" and "pick patterns".

Create the referenced `resources/implementation-playbook.md` (or remove the reference) and cite it once in the Resources section rather than three times.

Add an explicit validation/verification checkpoint (e.g. run the async test suite and confirm no unhandled coroutine warnings) to the implementation workflow.

DimensionReasoningScore

Conciseness

The body is mostly lean lists without explaining concepts Claude already knows, but the intro line restates the description and the reference to `resources/implementation-playbook.md` is repeated three times (Instructions, standalone line, and Resources), which is redundant padding.

2 / 3

Actionability

The Instructions are directives ("Add timeouts, backpressure, and structured error handling", "Pick concurrency patterns") with no executable code, commands, or concrete examples; all detail is deferred to a resource that is not present, so it describes rather than instructs.

1 / 3

Workflow Clarity

A sequence is present (clarify workload → pick patterns → add timeouts/error handling → include testing) but there are no explicit validation checkpoints or feedback loops, so checkpoints are missing or implicit.

2 / 3

Progressive Disclosure

Sections are cleanly organized and the reference is one level deep, but the referenced `resources/implementation-playbook.md` does not exist in the bundle and is referenced redundantly three times, so navigation is broken rather than well-structured.

2 / 3

Total

7

/

12

Passed

Description

80%

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 clearly answers both what the skill does and when to use it with strong, domain-appropriate trigger terms. Its main weakness is the imperative "Master" voice and an abstract action verb instead of concrete capabilities.

Suggestions

Rewrite in third person with concrete actions, e.g. "Implements asyncio patterns, concurrent task orchestration, and async/await workflows for high-performance applications."

Replace the abstract verb "Master" with specific capabilities the skill performs (orchestrates, schedules, cancels, applies backpressure).

DimensionReasoningScore

Specificity

The only action verb is the abstract "Master", naming the domain (asyncio, concurrent programming, async/await) but no concrete actions; base specificity is 2, reduced by 1 because "Master" is imperative/second-person voice rather than the third-person voice required by the guidelines.

1 / 3

Completeness

It states what it does ("Master Python asyncio... patterns for high-performance applications") and has an explicit "Use when building async APIs, concurrent systems, or I/O-bound applications" trigger, satisfying both what and when.

3 / 3

Trigger Term Quality

Phrases like "async APIs", "concurrent systems", "I/O-bound applications", and "async/await" give good coverage of natural terms a user would say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The async Python niche with triggers like "async APIs" and "I/O-bound applications requiring non-blocking operations" is distinct and unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.