Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable and well-structured with executable code and real one-level-deep references, but it is slightly redundant with the frontmatter description and lacks explicit validation/feedback checkpoints for migration and auth setup. It is strong overall with room to tighten and add verify steps.
Suggestions
Remove or trim the redundant intro sentence and the 'When to Use' list, since the frontmatter description already covers what the skill is and when to use it — this would tighten conciseness toward the top anchor.
Add an explicit validation/feedback loop around the database step, e.g. after 'npx @better-auth/cli generate' verify the schema, and after setup run a sanity check (e.g. hit the auth health endpoint) before proceeding to UI work.
Replace 'powerful plugin ecosystem' with a concrete statement of what the plugins enable, to avoid filler while keeping the same information value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient (code, tables, checklist), but the opening line 'Better Auth is comprehensive, framework-agnostic authentication/authorization framework for TypeScript with built-in email/password, social OAuth, and powerful plugin ecosystem' and the 'When to Use' list restate the frontmatter description, and 'powerful plugin ecosystem' is mild filler — tightening opportunities keep it off the top anchor. | 2 / 3 |
Actionability | It provides copy-paste-ready, executable guidance throughout — 'npm install better-auth', a complete auth.ts server config, 'npx @better-auth/cli generate', the Next.js handler, the auth-client setup, and signUp/signIn/session code samples — matching the 'fully executable code/commands' anchor. | 3 / 3 |
Workflow Clarity | A clear sequence exists (Quick Start steps plus an Implementation Checklist), but schema migration and auth setup are fragile operations with no explicit validate→fix→retry checkpoint; 'Test complete auth flow' is implicit verification rather than a feedback loop, so the validation-gaps cap applies. | 2 / 3 |
Progressive Disclosure | The body is an overview that points to four real one-level-deep reference files via the Feature Selection Matrix and the Reference Documentation section (e.g. '[email-password-auth.md](./references/email-password-auth.md)'), each verified to exist, giving clear navigation without nested references. | 3 / 3 |
Total | 10 / 12 Passed |