zod

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

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 77/100, solid C-grade territory. This is based on Anthropic's skill best practices framework. Your strongest area is Ease of Use (22/25)—the metadata and triggers are really well thought out. The weakest link is Progressive Disclosure Architecture (20/30)—you've got good content, but it's all packed into one file and could be structured more efficiently.

What's Working Well

• Trigger coverage is chef's kiss – You've got specific regex patterns like z\.object and semantic intent triggers like "validate input with TypeScript types". That's the kind of specificity that actually gets skills activated when developers need them.

• Practical examples – Your three few-shot_examples with input/output/reasoning are solid. They address real pain points (v3→v4 migration) and show developers exactly how to apply the patterns.

• Clear constraints – You're upfront about what this skill covers (Zod v4) and what it doesn't. No hand-waving. That's good meta-awareness.

The Big One

You need a table of contents and reorganized structure. Right now you've got ~395 lines crammed into one SKILL.md file with implicit navigation through XML tags. That works, but it leaves +2-4 points on the table.

Here's what I'd do:

• Add a markdown TOC after the frontmatter listing Quick Start → Patterns → Constraints → Anti-Patterns → Examples
• Extract your three detailed examples to references/examples.md (keeps the main file leaner, easier to scan)
• Keep one minimal example inline for quick reference

Impact: This alone gets you +2 points closer to 80.

Other Things Worth Fixing

1. Merge anti-patterns into constraints – Right now you're saying the same things twice ("Using .describe() in v4" appears in both sections). Consolidate into one "Do's and Don'ts" section with clear callouts. That's a token efficiency win and clears up ~1 point.

2. Add a numbered workflow – Your success_criteria checklist is helpful, but there's no explicit 1-2-3 flow for building a schema from scratch. Add a <workflow> section: 1) Define base schema 2) Add .meta() 3) Export types 4) Write tests. Gets you +2 points on Ease of Use.

3. Bump description trigger phrases – You've got solid triggers in the metadata, but the description itself is short on "when to use this" language. Add 2-3 more intent phrases like "type-safe runtime validation" or "schema composition patterns". Low-hanging fruit for spec compliance (+1).

Quick Wins

• Most impactful: Extract examples → add TOC → reorganize. That's +4 points and keeps your file scannable.
• Next: Merge anti-patterns + add workflow = +3 more points.
• Then: Beef up description trigger phrases = +1.

You're close to B-territory (80+). These structural tweaks won't take long and will push you there.

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.