Better Auth Best Practices
CheckedHelps with authentication, best practices as part of implementing security and authentication workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add autumnsgrove/lattice --skill better-auth-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
autumnsgrove
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
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 autumnsgrove/groveengine at edebdc71a7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- edebdc71a7
- Scanned
- 1 file, 728 lines
About this skill
What it does
This skill provides guidance and recommendations for implementing robust authentication practices in AI agent applications. It focuses on security best practices to protect user data and prevent unauthorized access, covering topics from password management to multi-factor authentication. The goal is to help developers build secure and trustworthy AI agents.
When to use it
- When designing the authentication flow for a new AI agent application.
- During code reviews of existing AI agent applications to identify potential security vulnerabilities related to authentication.
- To evaluate and improve the current authentication methods used by an AI agent, particularly when dealing with sensitive user data.
- When integrating third-party services or APIs that require secure authentication protocols.
Key capabilities
- Provides recommendations for password storage and hashing techniques.
- Offers guidance on implementing multi-factor authentication (MFA).
- Suggests best practices for session management and token security.
- Covers strategies to prevent common authentication attacks like brute force and credential stuffing.
Example prompts
- "What are the most secure ways to store user passwords in my AI agent application?"
- "How can I implement multi-factor authentication for my AI agent?"
- "Can you review my current session management code and identify any potential security risks?"
Tips & gotchas
This skill assumes a basic understanding of web development and security principles. While it offers best practices, implementing them requires careful consideration of the specific application context and potential trade-offs between security and usability.