api

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

Links:

• GitHub
• Your skill in the SkillzWave marketplace

The TL;DR

You're at 82/100, solid B grade territory. This is based on Anthropic's skill best practices. Your strongest area is Spec Compliance (14/15) — the frontmatter is clean and your description nails the trigger patterns. Where you're losing points: PDA (26/30) and Utility (18/20) — both have fixable gaps that could push you closer to 90.

What's Working Well

• Spec Compliance is nearly perfect — Valid YAML, correct hyphen-case naming, third-person description with extensive regex patterns. That's the foundation done right.
• Smart trigger patterns — You're covering library name (oRPC), file patterns (router.ts), and user intent ('create oRPC route'). That's comprehensive activation.
• Clear scaffolding approach — The 5-file pattern with layered routers (domain → action) is a solid mental model, and you've backed it with templates that have meaningful placeholders.
• Good token economy — Each section in SKILL.md earns its place. No fluff.

The Big One: Missing Concrete End-to-End Example

This is what's holding back your Utility score (18/20). Your quick_start section shows file structure, but doesn't show an actual implementation. Someone reading this skill should see:

// Example: token.transfer route
// File: routes/token/token.transfer.contract.ts
export const transfer = (context: Context) => ({
  // actual business logic here
})

Right now, developers have to infer how to populate those templates. Adding 4-5 code snippets showing a complete token.transfer implementation with real values would bridge that gap and add ~1-2 points to your Utility score.

Other Things Worth Fixing

1. **`tem...