CtrlK
BlogDocsLog inGet started
Tessl Logo

better-auth-best-practices

Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

54

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/better-auth-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a dense, well-structured reference guide with concrete commands and config, strong on actionability and conciseness, but it is reference-style rather than a validated workflow and provides no end-to-end integration example.

Suggestions

Add a short sequenced quick-start workflow with an explicit validation checkpoint after the `migrate` command.

Provide one complete minimal `auth.ts` config example so the pieces compose into copy-paste-ready guidance.

Consider moving the full config-options table and plugin catalog into a reference bundle file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is efficient — compact tables for config options, terse bullet lists for CLI commands and gotchas — with only minor over-explanation (e.g., the opening restatement of what Better Auth is) that could be trimmed.

4 / 5

Actionability

It provides concrete executable CLI commands (npx @better-auth/cli migrate), specific config keys with values, and a code snippet for plugin imports, but lacks a complete copy-paste end-to-end config example tying the pieces together.

4 / 5

Workflow Clarity

Content is organized as a topic reference rather than a sequenced workflow, and the destructive database `migrate` operation has no validation/verification checkpoint, which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

The single file is well-sectioned with clear headers and clearly signaled external doc URLs; no bundle files exist, and the content is appropriately organized, though a large reference table could eventually justify a split file.

4 / 5

Total

15

/

20

Passed

Description

52%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 identifies the named framework and its niche, but it is thin: it states only one generic action and omits any explicit trigger guidance for when to invoke the skill.

Suggestions

List concrete capabilities (e.g., configure email/password, OAuth, sessions, plugins) instead of the single generic verb "integrating".

Add an explicit "Use when..." clause naming natural trigger phrases (authentication, login, auth setup, OAuth, Better Auth).

Include synonyms and file/config triggers users actually say to raise trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("integrating Better Auth") but the action is generic and minimal — a single verb with no concrete capabilities like configuring sessions, plugins, or OAuth listed.

2 / 5

Completeness

It gives a clear "what" (integrating Better Auth, a TypeScript auth framework) but provides no "when"/"Use when..." trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

It includes relevant keywords ("Better Auth", "authentication", "TypeScript") but misses common natural variations a user might say such as "login", "auth setup", "OAuth", or "sign in".

3 / 5

Distinctiveness Conflict Risk

Naming the specific framework "Better Auth" carves a clear niche distinct from other auth skills (NextAuth, Clerk, Auth.js) with minimal conflict risk.

5 / 5

Total

13

/

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
novuhq/novu
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.