better-auth

Guide for implementing Better Auth - a framework-agnostic authentication and authorization framework for TypeScript. Use when adding authentication features like email/password, OAuth, 2FA, passkeys, or advanced auth functionality to applications.

Quality

83%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted description that clearly identifies the specific framework (Better Auth), its purpose (authentication/authorization), and provides explicit trigger guidance with natural keywords. The main weakness is that the 'what' portion could be more action-oriented (e.g., 'Configure and implement' rather than 'Guide for implementing').

Suggestions

Replace 'Guide for implementing' with more concrete action verbs like 'Configure, implement, and integrate Better Auth' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (authentication framework) and lists several features (email/password, OAuth, 2FA, passkeys), but uses 'Guide for implementing' which is somewhat vague about concrete actions. Doesn't specify actions like 'configure', 'set up', or 'integrate'.	2 / 3
Completeness	Clearly answers both what ('implementing Better Auth - a framework-agnostic authentication and authorization framework') and when ('Use when adding authentication features like email/password, OAuth, 2FA, passkeys, or advanced auth functionality to applications').	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'authentication', 'email/password', 'OAuth', '2FA', 'passkeys', 'auth functionality'. Also includes the specific framework name 'Better Auth' which is essential for targeted selection.	3 / 3
Distinctiveness Conflict Risk	The specific framework name 'Better Auth' combined with 'TypeScript' and the enumerated auth methods (passkeys, 2FA, OAuth) creates a clear niche. Unlikely to conflict with generic auth skills or other framework-specific auth skills.	3 / 3
	Total	11 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, highly actionable skill with excellent code examples covering the full Better Auth implementation workflow. The main weaknesses are moderate verbosity in introductory sections and a monolithic structure that could benefit from splitting advanced topics into separate reference files. The step-by-step setup and implementation checklist provide good workflow clarity.

Suggestions

Remove or significantly trim the 'When to Use This Skill' and 'Core Concepts > Key Features' sections - Claude doesn't need to be told when to use auth or what 'framework agnostic' means

Split advanced content (plugins, framework-specific guides, troubleshooting) into separate files like PLUGINS.md, FRAMEWORKS.md, and reference them from the main skill

Remove the 'Best Practices' section - these are generic software engineering practices Claude already knows

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some unnecessary explanations (e.g., 'Better Auth is a comprehensive, framework-agnostic authentication...' introduction, 'When to Use This Skill' section). The 'Core Concepts' section explains features Claude already knows. However, the code examples are lean and the overall structure avoids excessive verbosity.	2 / 3
Actionability	Excellent actionability with fully executable, copy-paste ready code examples for every major feature. Installation commands, configuration snippets, and client usage patterns are all concrete and complete. Multiple framework examples (Next.js, Nuxt, SvelteKit, Hono, Express) provide specific guidance.	3 / 3
Workflow Clarity	Clear step-by-step setup process (Steps 1-7) with explicit sequencing. The implementation checklist at the end provides validation checkpoints. Plugin workflow includes explicit migration step ('After Adding Plugins' section). The numbered steps make the multi-step process unambiguous.	3 / 3
Progressive Disclosure	The skill is quite long (~600 lines) and could benefit from splitting advanced topics (plugins, framework-specific guides, troubleshooting) into separate files. While sections are well-organized with clear headers, the monolithic structure means users must scroll through extensive content. References to external docs exist but internal file splitting would improve navigation.	2 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (720 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: einverne/dotfiles
Commit: b1b2fe0

Reviewed: 27 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.