Skip to content
TrustedSkillsbeta
Back to all skills

Clerk Auth

Listed
sickn33·vlatest·security·MIT

Automates verification of clerk authorization records against external databases to detect fraud and policy violations.

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 sickn33/agentic-awesome-skills --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

sickn33

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.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Commit
5a4cdd9df8
Manifest
skills/clerk-auth/SKILL.md
Scanned
0 files
Copies in repo
3 — all of them scanned
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 clerk-auth skill provides authentication and user management capabilities for AI agents, enabling secure access control and identity verification. It integrates with Clerk, a modern authentication platform, to handle user sign-ups, logins, and session management efficiently.

When to use it

  • When building an application that requires user authentication and role-based access control.
  • To streamline the process of managing user identities without manually implementing authentication logic.
  • For developers looking to quickly add secure login functionality to their AI agent workflows or web applications.
  • In scenarios where third-party authentication providers need to be integrated with minimal setup.

Key capabilities

  • User sign-up and login management
  • Role-based access control (RBAC) integration
  • Session handling and token generation
  • Seamless Clerk API integration

Example prompts

  • "Set up user authentication using Clerk for my web app."
  • "Generate a secure session token for the logged-in user."
  • "Restrict access to this feature only for admin users."

Tips & gotchas

  • Ensure you have a Clerk account and API keys configured before using this skill.
  • Be mindful of rate limits and security best practices when handling user data and tokens.