Skip to content
TrustedSkillsbeta
Back to all skills

Clerk Auth

Checked
sebas-aikon-intelligence·vlatest·security·MIT

Authenticates user access requests against multiple intelligence sources to verify identity and prevent unauthorized data exposure.

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 sebas-aikon-intelligence/antigravity-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

sebas-aikon-intelligence

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 sebas-aikon-intelligence/antigravity-awesome-skills at 0f4a1b2fd7.

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

Commit
0f4a1b2fd7
Manifest
skills/clerk-auth/SKILL.md
Scanned
1 file, 57 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 sebas-aikon-intelligence-clerk-auth skill provides authentication capabilities for AI agents. It allows agents to securely verify user identities and manage access based on those credentials, enabling secure interactions with protected resources or services. This skill integrates with Clerk Auth, a popular authentication platform.

When to use it

  • Secure Data Access: Grant an agent access to sensitive customer data only after verifying their identity through Clerk Auth.
  • Controlled API Interactions: Allow an AI agent to interact with APIs that require user authentication and authorization.
  • Personalized User Experiences: Tailor the agent's responses and actions based on authenticated user profiles stored in Clerk Auth.
  • Automated Workflows: Automate tasks requiring secure login, such as submitting forms or updating records within a protected system.

Key capabilities

  • Integration with Clerk Auth platform
  • User authentication via Clerk Auth
  • Secure credential management
  • Access control based on user roles and permissions

Example prompts

  • "Authenticate the user with email '[email protected]' and password 'password'."
  • "Check if the current user is authorized to access resource X."
  • "Retrieve the user’s profile information from Clerk Auth after successful login."

Tips & gotchas

  • Requires a Clerk Auth account and API keys for proper functionality.
  • Ensure the agent has the necessary permissions within Clerk Auth to perform the requested actions.