Skip to content
TrustedSkillsbeta
Back to all skills

Authjs Skills

Checked
gocallum·vlatest·security

Authjs Skills provides pre-built JavaScript authentication and authorization logic for your projects, streamlining security implementation.

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 gocallum/nextjs16-agent-skills --skill authjs-skills -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

gocallum

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.

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 gocallum/nextjs16-agent-skills at 531ee5767d.

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

Scanned
1 file, 1,076 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

The authjs-skills skill provides authentication and user management capabilities for AI agents, enabling secure login, session handling, and access control. It integrates with Auth.js to support various authentication providers like OAuth, email, and password-based systems.

When to use it

  • When building an application that requires user authentication and authorization.
  • For managing user sessions in a Next.js environment using Auth.js.
  • When implementing secure login flows for AI agents or web applications.
  • To enable third-party sign-in options like Google, GitHub, or Twitter.

Key capabilities

  • Integration with Auth.js for authentication workflows
  • Support for multiple authentication providers (OAuth, email, password)
  • Session management and user access control
  • Compatibility with Next.js 16 and modern web frameworks

Example prompts

  • "Set up OAuth login using Google with Auth.js."
  • "Implement secure session handling in a Next.js app."
  • "Add email-based authentication to my AI agent platform."

Tips & gotchas

  • Ensure you have a working Next.js project before installing this skill.
  • Authentication flows may require backend configuration and API keys from third-party providers.