CtrlK
BlogDocsLog inGet started
Tessl Logo

better-auth

TypeScript authentication framework (framework-agnostic). Features: email/password, OAuth (Google, GitHub, Discord), 2FA (TOTP, SMS), passkeys/WebAuthn, session management, RBAC, rate limiting, database adapters. Actions: implement, configure, secure authentication systems. Keywords: Better Auth, authentication, authorization, OAuth, email/password, 2FA, MFA, TOTP, passkeys, WebAuthn, session management, RBAC, rate limiting, database adapter, TypeScript auth, social login, Google auth, GitHub auth, Discord auth, email verification, password reset. Use when: implementing TypeScript auth, adding OAuth providers, setting up 2FA/MFA, managing sessions, configuring RBAC, building secure auth systems.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%Weight 40%Scale 1-5

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

The body is a well-structured, actionable overview with excellent progressive disclosure and copy-paste-ready code. Its weak point is workflow clarity: the database-migration path lacks explicit validation checkpoints and error-recovery feedback loops.

Suggestions

Add an explicit validation step after 'npx @better-auth/cli generate/migrate' (e.g. verify the schema applied cleanly, retry on failure) to introduce a feedback loop for the destructive database operation.

Trim the 'Auth Method Selection Guide' or fold it into the Feature Selection Matrix to remove guidance Claude can infer, improving conciseness.

Remove the 'When to Use' section in the body since it duplicates the frontmatter description's trigger guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable code blocks and no explanation of basic concepts, but the 'When to Use' section overlaps the description and the 'Auth Method Selection Guide' offers somewhat inferable guidance that could be trimmed.

4 / 5

Actionability

Quick Start provides copy-paste-ready, executable guidance end-to-end — install, env, server instance, schema generation/migration commands, handler mounting, client, and sign-up/sign-in/OAuth/session usage — covering the common cases.

5 / 5

Workflow Clarity

Steps are clearly sequenced (install → env → server → schema → handler → client → usage) with an implementation checklist, but the database-migration step ('npx @better-auth/cli migrate') lacks an explicit validate/verify checkpoint or failure feedback loop, which caps workflow clarity at 3 for database operations.

3 / 5

Progressive Disclosure

SKILL.md is a concise overview with a Feature Selection Matrix linking to verified one-level-deep reference files at specific anchors, plus separate scripts and a reference-docs section — content is appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

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

The description clearly states what the skill does and when to use it, with a strong, natural keyword set and a distinct niche. Its main weakness is mild keyword-stuffing verbosity and slightly abstract action verbs rather than granular operations.

Suggestions

Tighten the Keywords block by removing near-duplicates (e.g. '2FA' and 'MFA' alongside 'TOTP') so the description reads as natural prose rather than a tag list.

Replace abstract action verbs ('implement, configure, secure') with more concrete operations (e.g. 'add OAuth providers', 'set up 2FA flows', 'migrate auth schemas').

DimensionReasoningScore

Specificity

Lists concrete actions ('implement, configure, secure authentication systems') plus a comprehensive feature set (email/password, OAuth, 2FA, passkeys, RBAC, etc.), but the named actions are higher-level category verbs than the granular 'extract/fill/merge' style of the score-5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' (TypeScript authentication framework with enumerated features) and 'when' via a concrete 'Use when: implementing TypeScript auth, adding OAuth providers, setting up 2FA/MFA, managing sessions, configuring RBAC, building secure auth systems' clause.

5 / 5

Trigger Term Quality

A dedicated Keywords block covers natural terms and synonyms users would say — '2FA' and 'MFA', 'TOTP', 'passkeys', 'WebAuthn', 'social login', provider-specific phrasings ('Google auth', 'GitHub auth', 'Discord auth'), 'email verification', 'password reset' — giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

Names a specific framework (Better Auth) with a distinct TypeScript-auth niche and precise triggers, so it is unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
samhvw8/dot-claude
Reviewed

Table of Contents

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.