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 compl...