vitest

I took a look at your vitest skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 75/100, solid C-grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Spec Compliance (14/15) — the fundamentals are tight. Weakest is Progressive Disclosure Architecture (22/30) — there's some structural inefficiency that's eating your token economy.

What's Working Well

• Spec compliance is basically perfect (14/15). Your YAML frontmatter is clean, naming follows conventions, and your description has comprehensive trigger coverage (40+ patterns). This skill will activate on natural queries.
• Your trigger list is genuinely thorough — covering everything from explicit vi.fn, .test.ts, describe( to implicit "mock a service test" patterns. That's good UX design.
• The quick_start table is a solid entry point with clear scenarios, and your success_criteria checklist gives devs a real validation path. That's the kind of thing that makes a skill feel approachable.

The Big One: Token Waste From Duplication

Your mocking patterns appear twice — once inline in the <mocking> section (lines 110-123) and again in templates/mock-module.ts.md. For a 350-line file, this is burning tokens on repetition.

The fix: Keep only the vi.fn() basics in SKILL.md with a reference to the template. Move the full module mocking example into the template exclusively. This alone should save ~40 tokens and bump you +2 points toward 77/100.

Other Things Worth Fixing

1. Add a table of contents — 350+ lines without a TOC makes navigation a pain. Add a simple ## Contents section listing: objective, mocking, advanced patterns, assertions, templates, commands. G...