Skip to content
TrustedSkillsbeta
Back to all skills

Clerk Auth

Listed
jackspace·vlatest·security·MIT

Authenticates users against Jackspace systems using secure credentials and access controls.

Repository

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 jackspace/claudeskillz --skill clerk-auth -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

jackspace

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 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 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.clerk.com, clerk.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

    clerk.comundeclaredapi.clerk.comundeclared

    What it found (3 of 4)

    • skills/clerk-auth/SKILL.json:20contacts clerk.com
      "Next.js App Router Setup": "NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in\r\nNEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up\r\nNEXT_PUBLIC_CLERK_AFTER_SIGN_IN_URL=/dashboard…
    • skills/clerk-auth/SKILL.json:20contacts clerk.com
      "Next.js App Router Setup": "NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in\r\nNEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up\r\nNEXT_PUBLIC_CLERK_AFTER_SIGN_IN_URL=/dashboard…
    • skills/clerk-auth/SKILL.json:22contacts clerk.com
      "JWT Templates & Custom Claims": "Clerk allows customizing JWT (JSON Web Token) structure using templates. This enables integration with third-party services, …

  • 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 jackspace/claudeskillz at aef4e299d1.

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

Commit
aef4e299d1
Manifest
skills/clerk-auth/SKILL.md
Scanned
3 files, 930 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 integrates Clerk Auth, a popular authentication service, into your AI agent. It allows agents to securely manage user accounts, handle sign-in and sign-up flows, and potentially access protected resources based on user identity. The integration simplifies the process of adding robust authentication features to applications powered by AI agents.

When to use it

  • Building a membership site: Allow users to create accounts and log in to access exclusive content or features within your agent's application.
  • Creating personalized experiences: Authenticate users so your agent can tailor responses and actions based on their individual preferences and data.
  • Protecting sensitive resources: Restrict access to certain functionalities or information within the agent’s environment based on user authentication status.
  • Developing multi-user applications: Enable multiple users to interact with the agent independently, each with their own account and associated data.

Key capabilities

  • User sign-up functionality
  • User login/authentication
  • Account management features (potentially)
  • Secure user identity verification

Example prompts

  • "Authenticate this user: [user email address]"
  • "Create a new user account with the following details: [name, email, password]"
  • "Check if this user is logged in."

Tips & gotchas

  • Requires an active Clerk Auth project and API keys to function. Ensure these are properly configured within your agent's environment variables.