Skip to content
TrustedSkillsbeta
Back to all skills

Clerk Auth

Listed
ovachiever·vlatest·security

Authenticates user access to sensitive data and systems using multi-factor authentication and role-based permissions.

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 ovachiever/droid-tings --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

ovachiever

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, api.supabase.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

    api.supabase.comundeclaredapi.clerk.comundeclared

    What it found (3 of 6)

    • skills/clerk-auth/references/jwt-claims-guide.md:350contacts api.supabase.com
      const response = await fetch('https://api.supabase.com/endpoint', {
    • skills/clerk-auth/references/testing-guide.md:177contacts api.clerk.com
      curl -X POST https://api.clerk.com/v1/users \
    • skills/clerk-auth/references/testing-guide.md:206contacts api.clerk.com
      curl -X POST https://api.clerk.com/v1/sessions \

  • 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 ovachiever/droid-tings at 7acd12a754.

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

Commit
7acd12a754
Manifest
skills/clerk-auth/SKILL.md
Scanned
22 files, 3,698 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 ovachiever-clerk-auth skill enables AI agents to integrate with Clerk, a popular authentication service. It facilitates user sign-up and login flows within applications, securely managing user credentials and providing access control. This skill streamlines the process of building secure and authenticated experiences for users interacting with your agent.

When to use it

  • Building a membership site: Allow users to create accounts and log in to access exclusive content or features.
  • Creating a personalized application: Authenticate users so that the AI agent can tailor its responses and actions based on their profile.
  • Managing user data securely: Integrate Clerk's secure authentication system to protect sensitive user information.
  • Implementing multi-factor authentication (MFA): Enhance security by requiring users to verify their identity through multiple channels.

Key capabilities

  • User Sign-up
  • Login functionality
  • Secure credential management
  • Integration with Clerk authentication service
  • Multi-Factor Authentication (MFA) support

Example prompts

Tips & gotchas

  • Requires a Clerk API key to function correctly; ensure this is properly configured within your AI agent environment.
  • Clerk's pricing structure may apply depending on usage volume. Review Clerk’s documentation for details.