python-async

I took a look at your python-async skill and wanted to share some thoughts.

Links:

• GitHub
• Your skill in the SkillzWave marketplace

The TL;DR

You're at 75/100 — solidly competent work, but there's a gate-keeping issue preventing you from breaking into the 80s. Your writing is crisp (10/10 on style), the content structure is sensible, and the actual async guidance is comprehensive. But the frontmatter is broken, which tanks your spec compliance score to 0/15. Fix that one thing and you're probably looking at 84-86/100.

What's Working Well

• Writing clarity — You're using imperative form consistently ("Master Python asyncio..."), no fluff, reads like someone who knows the material. That perfect 10/10 on writing style isn't luck.
• Progressive disclosure — You've got 7 modules structured thoughtfully with the overview in SKILL.md and detailed modules one level deep. That's exactly what 27/30 on PDA looks like.
• Utility and examples — Rich code examples and clear pattern templates address real async pain points. Your triggers (concurrency, coroutines, await, async, asyncio) are solid and cover the problem space well.

The Big One: Broken Frontmatter

Your YAML frontmatter is malformed. The parser is choking on it — that's why spec compliance is 0/15. Here's what it should look like:

Current (broken):

---
name: python-async
description: |

Triggers: concurrency, coroutines, await, async, asyncio
  Master Python asyncio, concurrent programming, and async/await patterns...

Fixed:

---
name: python-async
description: Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when asked to "python async", "asyncio", "concurrent programming", or "async/await patterns".
tags: [concurrency, coroutines, await, async, asyncio]
---

This one fix alone bumps you up about 5 points just on frontmatter validity, plus 4 points for description quality and proper name handling. You're looking at +13 points just from getting the YAML valid.

Other Things Worth Fixing

1. Redundant triggers — You've got trigger terms scattered in the description AND in a separate line. Consolidate them into a single tags field in the frontmatter. Cleaner, better parsed, same info.

2. Add a table of contents — You've got 100+ lines with multiple sections. Pop a TOC at the top (## Quick Navigation or similar). Adds maybe 5 lines but nets you +2 points on navigation signals.

3. Exit criteria could be tighter — You have them, which is good, but they could be more specific about "user can do X" vs "system outputs Y". Small tweak for +1-2 points.

Quick Wins

• Fix the frontmatter YAML (validation + description quality) → +13 points
• Consolidate triggers to tags field → +2 points
• Add TOC at top → +2 points
• Tighten exit criteria → +1-2 points

You're probably looking at 90+ after these tweaks. The foundation is solid — it's just the metadata that needs attention.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.