vitest

I was checking out your vitest skill and noticed how you've structured the progressive disclosure—the way you layer from basic setup into advanced patterns really minimizes token overhead. With an 87/100, you're clearly nailing the practical stuff, but I'm curious whether you considered adding examples for some of the edge cases around test isolation or async handling that folks usually trip up on.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 87/100, solid B grade. This is based on Anthropic's best practices for agentic skills. Your strongest area is Writing Style (9/10)—the voice is imperative, concise, no fluff. Weakest is Spec Compliance (12/15), mainly because you're only hitting 1-2 trigger phrases when you could be more granular.

What's Working Well

• Progressive Disclosure is genuinely tight. Your three reference files (assertions.md, mocking.md, async.md) sitting below the main file is the right call. Separates overview from deep dives without bloating the core.
• Quick Start template hits the mark. You're giving developers something they can copy-paste immediately—describe, beforeEach, assertions. That's how you get adoption.
• Clear API language throughout. Using vi.fn, vi.mock, vi.waitFor consistently makes it obvious you're speaking Vitest, not generic testing concepts.

The Big One: Missing Navigation in Reference Files

Your reference files are getting meaty (assertions.md is 102 lines, mocking.md is 116 lines), but they lack a table of contents. When someone's scanning for "which assertion should I use for object comparison?" they're scrolling the whole file. A simple TOC at the top of each reference file gains you ~2 points and makes the skill way more usable.

Fix: Add this after the header in each reference...