Skip to content
TrustedSkillsbeta
Back to all skills

Clerk Auth

Checked
omer-metin·vlatest·security·Apache-2.0

Authenticates user access to sensitive documents and systems based on predefined rules and authorization protocols.

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 omer-metin/skills-for-antigravity --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

omer-metin

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 omer-metin/skills-for-antigravity at e8dcf4e873.

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

Commit
e8dcf4e873
Manifest
skills/clerk-auth/SKILL.md
Scanned
4 files, 1,598 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 omer-metin-clerk-auth skill integrates authentication functionality into AI agents using Clerk. This allows agents to securely manage user accounts, handle logins and signups, and protect sensitive data through a robust authentication system. It simplifies implementing secure access controls for agent interactions.

When to use it

  • Building Agents with User Accounts: When your agent needs to provide personalized experiences or restrict access based on individual users.
  • Secure Data Access: If the agent handles sensitive information, Clerk Auth provides a layer of security by authenticating users before granting access.
  • Multi-Factor Authentication (MFA): To enhance security beyond simple passwords, enabling MFA for user logins.
  • Social Login Integration: Allowing users to sign in using existing accounts from providers like Google or Microsoft.

Key capabilities

  • User account creation and management
  • Secure login and signup processes
  • Multi-factor authentication (MFA) support
  • Social login integration

Example prompts

  • "Create a new user account for John Doe with email [email protected]."
  • "Authenticate the current user using their Google account."
  • "Enable multi-factor authentication for this user."

Tips & gotchas

  • Requires a Clerk API key to function correctly; ensure it is properly configured within the agent's environment variables.
  • Clerk Auth handles the complexities of secure authentication, but understanding basic security principles remains important when designing your agent’s interactions.