Nextjs Better Auth Session Guard
CheckedHelps with Next.js, authentication as part of building frontend UIs and user experiences 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 hankanman/claude-config --skill nextjs-better-auth-session-guard -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
hankanman
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 hankanman/claude-config at 198c839ac0.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 198c839ac0
- Scanned
- 1 file, 386 lines
About this skill
What it does
This skill provides a Next.js component that acts as a session guard, protecting routes and pages based on authentication status. It automatically redirects unauthenticated users to a login page while allowing authenticated users access. The component simplifies the process of securing sensitive areas within a Next.js application by handling redirection logic.
When to use it
- Protecting admin dashboards or user profile sections that require login.
- Securing API routes that should only be accessible to authenticated users.
- Implementing role-based access control, ensuring certain pages are visible only to specific user roles.
- Creating a consistent authentication flow across your Next.js application without repetitive code.
Key capabilities
- Automatic redirection of unauthenticated users.
- Component-based integration within Next.js applications.
- Simplified session management for protected routes.
- Customizable login page URL configuration.
Example prompts
- "Wrap the
/dashboardroute with the session guard." - "Configure the session guard to redirect to
/loginwhen unauthenticated." - “Ensure that only logged-in users can access the
/profilepage.”
Tips & gotchas
- Requires a Next.js project and an existing authentication system for managing user sessions.
- The skill relies on properly configured session data within your Next.js application; ensure this is set up before implementation.