Better Auth Profile
ListedAnalyzes user authentication profiles to identify risky login patterns and potential compromise indicators.
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 andrelandgraf/fullstackrecipes --skill better-auth-profile -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
andrelandgraf
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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: fullstackrecipes.com.
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.
Hosts contacted
fullstackrecipes.comundeclaredWhat it found
- .agents/skills/better-auth-profile/SKILL.md:11contacts fullstackrecipes.com
curl https://fullstackrecipes.com/recipes/better-auth-profile.md
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 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 andrelandgraf/fullstackrecipes at 4449331ed5.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4449331ed5
- Scanned
- 1 file, 11 lines
About this skill
The better-auth-profile skill enables AI agents to securely manage user identity data within the BetterAuth framework. It allows agents to retrieve, update, and verify authenticated user profiles while maintaining strict access controls. This tool is essential for building applications that require persistent user sessions and personalized data access.
When to use it
- Implementing login flows where an AI agent needs to fetch a user's name or email after successful authentication.
- Updating user preferences or profile metadata dynamically based on interactions within a secure session.
- Verifying that a specific user is authenticated before granting access to sensitive dashboard features.
- Managing multi-tenant applications where the agent must distinguish between different user contexts.
Key capabilities
- Secure retrieval of authenticated user profile information.
- Dynamic updates to user data within an active session.
- Integration with BetterAuth's built-in security protocols for identity verification.
- Support for structured data access patterns required by full-stack recipes.
Example prompts
- "Retrieve the current user's email address from the authenticated session using better-auth-profile."
- "Update the user's display name to 'John Doe' and save the changes securely."
- "Check if the user is logged in and fetch their profile details before proceeding with the task."
Tips & gotchas
Ensure your AI agent has proper permissions configured within BetterAuth before attempting to read or modify profiles. Always validate that a valid authentication token exists in the session context before executing profile operations to prevent unauthorized access.