astro-patterns

I took a look at your astro-patterns skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 63/100 — solidly in D territory, and that's almost entirely because of a fixable frontmatter issue. Your writing is chef's kiss (10/10), and the actual content is genuinely useful with comprehensive Astro coverage. But the skill metadata is broken, which tanks your spec compliance to 0/15. Fix that and you're looking at 68+ points pretty quickly.

What's Working Well

• Writing style is tight — Imperative voice, no fluff, purely instructional. This is exactly how Claude skills should read.
• Solid utility — You've got practical templates, real troubleshooting sections, and examples that actually solve problems. The phased approach (routing, components, optimization) is smart.
• Good trigger coverage — "building Astro websites", "setting up routing", "component architecture" — these are discoverable and specific. Developers will find this.
• Workflow clarity — You've organized this with numbered steps and clear sections, which makes it easy to scan and follow.

The Big One: Fix Your Frontmatter

This is the hammer blow to your score. Your SKILL.md starts with invalid YAML — the description is truncated and the metadata section is malformed. This alone costs you 15 points (all of spec compliance).

Fix: Your frontmatter should look like this:

---
name: astro-patterns
description: Astro best practices, routing patterns, component architecture, and static site generation techniques. Use when asked to "build Astro website", "set up Astro routing", "design Astro components", or "optimize Astro site".
---

Make sure it's complete, properly closed, and the description includes 3-4 concrete trigger phrases. Takes 5 minutes, gains you 15 points.

Other Things Worth Fixing

1. Move content to a layered structure — Right now it's all in one 519-line file. Break this into references/ subdirectories for templates, setup scripts, and troubleshooting guides. You'll pick up ~7 points and make the skill way easier to navigate.

2. Add a table of contents — For a skill this length, a TOC after the overview helps people jump to what they need. Small win (~2 points), big usability bump.

3. Implement the references you mention — You reference things like "scripts/setup-routing.sh" but they don't exist as actual files. Create those reference files or remove those references. This fixes the "references not implemented" issue.

Quick Wins

• Fix frontmatter metadata (+15 points) — Takes 5 minutes, biggest bang for buck
• Create layered structure with references/ (+7 points) — Move templates/scripts to separate files
• Add table of contents (+2 points) — Helps with 519-line file navigation
• Remove/implement dangling script references — Cleans up the integrity issue

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.