better-auth-setup

1 stars 2 forks
17
C

Guide implementation of OAuth 2.1 / OIDC authentication using Better Auth with the OIDC Provider plugin. Use this skill when setting up centralized authentication for multiple apps, implementing SSO across a platform, creating an OAuth authorization server, or integrating Better Auth as an identity provider. Covers PKCE for public clients, JWKS configuration, token management, email verification, and common pitfalls like preserving PKCE parameters during sign-in redirects.

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install mjunaidca/mjs-agent-skills/better-auth-setup
skilz install mjunaidca/mjs-agent-skills/better-auth-setup --agent opencode
skilz install mjunaidca/mjs-agent-skills/better-auth-setup --agent codex
skilz install mjunaidca/mjs-agent-skills/better-auth-setup --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/mjunaidca/mjs-agent-skills
2. Copy the agent skill directory:
cp -r mjs-agent-skills/docs/taskflow-vault/skills/engineering/better-auth-setup ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Stars
1
Forks
2
Type
Technical
Meta-Domain
web api
Primary Domain
security
Market Score
17

Agent Skill Grade

C
Score: 75/100 Click to see breakdown

Score Breakdown

Spec Compliance
11/15
PDA Architecture
18/30
Ease of Use
21/25
Writing Style
8/10
Utility
17/20

Areas to Improve

  • Description needs trigger phrases
  • Missing Layered Structure
  • No Table of Contents

Recommendations

  • Address 1 high-severity issues first
  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-24

Developer Feedback

Found your skill while auditing authentication patterns—the approach to streamlining Better Auth setup caught my attention, though there's clearly room to tighten up the execution based on the 75/100. What's your philosophy on balancing simplicity with edge-case handling in auth flows?

Links:

The TL;DR

You're at 75/100, solid C-grade territory. This is based on Anthropic's Progressive Disclosure Architecture best practices for agentic skills. Strongest area: Utility (17/20)—your PKCE implementation and email verification approach are genuinely useful. Weakest area: Progressive Disclosure Architecture (18/30)—everything's crammed into one 582-line file without layering or references, which burns tokens and makes navigation painful.

What's Working Well

  • Excellent utility focus: You're solving real problems (PKCE for public clients, email verification workflows, admin endpoints). The Common Pitfalls section is particularly good—it shows you've thought through what actually breaks in production.
  • Strong metadata and discoverability: Your triggers are specific (OAuth authorization server, PKCE, OIDC, SSO) and the description clearly states when to use this skill. That's a solid foundation for marketplace discovery.
  • Practical checklists: The testing checklist and security checklist give developers actionable verification steps. That feedback loop matters.
  • Comprehensive code examples: Your database schema, TypeScript implementations, and configuration sections are detailed enough to actually follow.

The Big One: Break It Into Layers

Your main blocker is Progressive Disclosure Architecture—you've got 582 lines in a single file trying to cover JWKS c...

Report Security Issue

Found a security vulnerability in this agent skill?