How do I install the Better Auth skill?

Run npx skillmds@latest add blogic-cz/better-auth in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Better Auth safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Better Auth?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Better Auth free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Better Auth?

blogic-cz (@blogic-cz) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Better Auth by blogic-cz — Agent Skill

Name: Better Auth
Author: blogic-cz

File contents

Better Auth Procedure Selection

Select authorization boundaries with Better Auth + TRPC patterns used in template-ts apps.

Procedure Selection Table

Procedure	Access Level	Context Provided
`publicProcedure`	No auth	`{ db, session?, headers }`
`protectedProcedure`	Authenticated	`{ db, session, userId, headers }`
`adminProcedure`	Admin role	`{ db, session, headers }`
`protectedOrganizationMemberProcedure`	Org member	`{ ..., member, organizationId }`
`protectedOrganizationAdminProcedure`	Org admin/owner	`{ ..., member, organizationId }`
`protectedProjectMemberProcedure`	Project access	`{ ..., project, projectRole, orgRole }`
`protectedProjectAdminProcedure`	Project admin	`{ ..., project, projectRole, orgRole }`
`protectedProjectEditorProcedure`	Project editor+	`{ ..., project, projectRole, orgRole }`

Use this table as the primary selector before writing router logic.

Use This Skill When

Select the correct protected procedure for organization/project/member/admin access.
Implement Better Auth authorization checks inside TRPC procedures.
Review auth boundaries in existing routers.

Follow This Workflow

Identify required access level from the Procedure Selection Table.
Start implementation from the matching base procedure.
Chain stricter middleware only when the table does not fully satisfy the access rule.
Load references/better-auth-examples.md for detailed examples and copy-ready snippets.
Keep context shape stable; add only route-specific fields.

Key Rules

Select the narrowest procedure that matches the required permission.
Reuse inherited context (userId, organizationId, project, roles) instead of recomputing it.
Grant organization admins automatic project-admin behavior; avoid duplicate checks.
Pass ctx.headers to auth.api.* server calls.
Validate variable origins in every middleware (opts.ctx, opts.input) before adding business logic.

References

references/better-auth-examples.md — auth configuration, context setup, middleware examples, client auth usage, and admin API patterns.

---name: better-authdescription: This skill should be used when implementing or reviewing Better Auth authorization boundaries in template-ts apps, especially when selecting TRPC protected procedures for organization/project/member/admin access.---# Better Auth Procedure SelectionSelect authorization boundaries with Better Auth + TRPC patterns used in template-ts apps.## Procedure Selection Table| Procedure | Access Level | Context Provided || -------------------------------------- | --------------- | ---------------------------------------- || `publicProcedure` | No auth | `{ db, session?, headers }` || `protectedProcedure` | Authenticated | `{ db, session, userId, headers }` || `adminProcedure` | Admin role | `{ db, session, headers }` || `protectedOrganizationMemberProcedure` | Org member | `{ ..., member, organizationId }` || `protectedOrganizationAdminProcedure` | Org admin/owner | `{ ..., member, organizationId }` || `protectedProjectMemberProcedure` | Project access | `{ ..., project, projectRole, orgRole }` || `protectedProjectAdminProcedure` | Project admin | `{ ..., project, projectRole, orgRole }` || `protectedProjectEditorProcedure` | Project editor+ | `{ ..., project, projectRole, orgRole }` |Use this table as the primary selector before writing router logic.## Use This Skill When- Select the correct protected procedure for organization/project/member/admin access.- Implement Better Auth authorization checks inside TRPC procedures.- Review auth boundaries in existing routers.## Follow This Workflow1. Identify required access level from the Procedure Selection Table.2. Start implementation from the matching base procedure.3. Chain stricter middleware only when the table does not fully satisfy the access rule.4. Load `references/better-auth-examples.md` for detailed examples and copy-ready snippets.5. Keep context shape stable; add only route-specific fields.## Key Rules1. Select the narrowest procedure that matches the required permission.2. Reuse inherited context (`userId`, `organizationId`, `project`, roles) instead of recomputing it.3. Grant organization admins automatic project-admin behavior; avoid duplicate checks.4. Pass `ctx.headers` to `auth.api.*` server calls.5. Validate variable origins in every middleware (`opts.ctx`, `opts.input`) before adding business logic.## References- `references/better-auth-examples.md` — auth configuration, context setup, middleware examples, client auth usage, and admin API patterns.

Frequently asked questions

Better Auth