CtrlK
BlogDocsLog inGet started
Tessl Logo

better-auth-best-practices

Better Auth server/client setup: `auth.ts`, generated schema, DB adapters, sessions, cookies, env vars, and plugins. Use when mentioning Better Auth, betterauth, auth handlers, OAuth, email/password, or session configuration.

68

Quality

81%

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

75%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.

A dense, well-organized reference guide with actionable commands and a clear setup workflow including verification. It would benefit from error-recovery feedback loops and splitting bulk reference material into separate bundle files.

Suggestions

Add an explicit error-recovery feedback loop after the migrate/verify steps (e.g., if GET /api/auth/ok fails, check env vars and re-run migrate).

Move the bulk config-option tables and gotchas into separate reference bundle files (e.g. reference/options.md, reference/gotchas.md) and link to them from SKILL.md to improve progressive disclosure.

Tighten the Security and Hono/OAuth prose sections into bullet-form checklists to reduce token cost while preserving the security guidance.

DimensionReasoningScore

Conciseness

Mostly lean with terse tables and bullets and no concept padding, though a few prose sections (Security, Hono/OAuth boundaries) could be tightened further.

4 / 5

Actionability

Provides concrete commands, import paths, env-var generation, and config keys throughout, but the config table presents keys with notes rather than fully copy-paste ready snippets.

4 / 5

Workflow Clarity

Setup Workflow is a clear numbered sequence with an explicit verification checkpoint (GET /api/auth/ok), but lacks an explicit error-recovery feedback loop for migrate/verify failures.

4 / 5

Progressive Disclosure

Single file with well-organized section headers and one-level-deep external links, but bulk reference content (config tables, gotchas) is inlined rather than split into bundle reference files despite the skill's size.

4 / 5

Total

16

/

20

Passed

Description

87%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.

A strong, well-structured description that clearly states capabilities and explicit use-when triggers tied to a specific framework. Minor room to add synonyms and file extensions for broader natural-term coverage.

DimensionReasoningScore

Specificity

Enumerates concrete setup objects and actions (auth.ts, generated schema, DB adapters, sessions, cookies, env vars, plugins), listing several specifics, though it leans on nouns over verbs and leaves minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (server/client setup with listed components) and when ('Use when mentioning Better Auth, betterauth, auth handlers, OAuth...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides good natural trigger coverage (Better Auth, betterauth, OAuth, email/password, session configuration) but omits file extensions and synonyms like 'login' or 'auth flow'.

4 / 5

Distinctiveness Conflict Risk

Tied to a named framework (Better Auth) with product-specific triggers, giving a clear niche and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EpicenterHQ/epicenter
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.