better-auth

I took a look at your better-auth skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 76/100, solidly in C territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Spec Compliance (14/15) — the frontmatter and naming conventions are tight. The weakest is Utility (15/20) — you've got good setup examples, but missing troubleshooting, verification loops, and templates that would make this genuinely useful for developers trying to integrate Better Auth.

What's Working Well

• Excellent metadata and triggers — Your frontmatter covers library names, API patterns, hooks, and specific user intents like "passkey", "social", "2fa". This is going to surface the skill in the right contexts.
• Clean terminology consistency — You clearly distinguish between server-side betterAuth and client-side authClient APIs throughout. That's exactly what developers need.
• Solid quick-start structure — The 5-step workflow is logical and gets someone from zero to a working integration pretty quickly.

The Big One: Missing Verification & Troubleshooting

Why it matters: Developers will follow your setup steps, but they need feedback that it actually worked. Right now, your workflow has no validation between steps — step 3 is "install packages" and then you jump to "create handler" with zero confirmation.

Concrete fix:

• After Step 3 (install packages), add: Verify: npm run build && npm start with expected output
• Add a new section <troubleshooting> with common errors:
  • "BETTER_AUTH_SECRET not found" → "Generate with: openssl rand -hex 32"
  • "Port 3000 in use" → "Use a different port in config"
• Create references/env-template.md with a complete .env.example file

Impact: This alone gets you +3-4 points by addressing the "feedback loops" and "verification patterns" gaps.

Other Things Worth Fixing

1. Redundant MCP examples — Your <mcp_first> and <research> sections both show similar OctoCode search patterns. Consolidate to one section with 2 essential examples. Saves tokens, gains clarity.

2. No table of contents for a 279-line file — Add a brief TOC after the frontmatter listing your XML sections. At this length, navigation matters.

3. Missing plugin reference docs — Your plugins table is 5 rows with one-word descriptions. Create references/plugins.md with actual configuration examples for passkey setup and organization plugins. That's where the real depth lives.

4. Marketing language in the evolution section — "TypeScript-first patterns that evolve with the ecosystem" reads like promotional copy. Reframe as: "Compatible patterns as the TypeScript ecosystem evolves."

Quick Wins

• Add 1 verification step between setup phases (+2 pts)
• Create .env.example template (+1 pt)
• Consolidate MCP examples to remove redundancy (+2 pts)
• Add brief TOC for navigation (+1 pt)
• Rewrite one marketing phrase in evolution section (+1 pt)

Do those five and you're easily at 85+. The skill has good bones — it just needs some developer-facing scaffolding that helps people verify they got it right.

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.