Skip to content
TrustedSkillsbeta
Back to all skills

Better Auth Integration Guide

Official
better-auth·vlatest·security

Helps with authentication, best practices as part of implementing security and authentication workflows.

Repositoryskills.sh

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add better-auth/skills --skill better-auth-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

better-auth

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned better-auth/skills at 20c9e88a5c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
20c9e88a5c
Manifest
better-auth/best-practices/SKILL.md
Scanned
1 file, 191 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides best practices for authentication and authorization in software systems, including secure password handling, token management, session control, and role-based access. It helps developers implement robust security measures to protect user data and system integrity.

When to use it

  • When designing or reviewing an authentication system for a web application
  • When implementing multi-factor authentication (MFA) for user accounts
  • When setting up secure API endpoints that require token-based access

Key capabilities

  • Guidance on password hashing algorithms like bcrypt or Argon2
  • Recommendations for JWT (JSON Web Token) usage and expiration policies
  • Secure session management techniques, including regeneration and timeouts
  • Role-based access control (RBAC) implementation strategies

Example prompts

  • "How should I securely store user passwords in my application?"
  • "What are the best practices for managing API tokens with expiration times?"
  • "Can you explain how to implement role-based access control in a web app?"

Tips & gotchas

  • Always use well-established libraries for password hashing and token generation rather than implementing your own.
  • Regularly update dependencies to ensure they include the latest security patches.