Skip to content
TrustedSkillsbeta
Back to all skills

Clerk Auth

Checked
poletron·vlatest·security·CC0-1.0

Authenticates users against Poletron systems using secure credentials and verifies access 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 odjaramillo/custom-rules --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

poletron

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 poletron/custom-rules at aba6668777.

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

Commit
aba6668777
Manifest
registry/skills/clerk-auth/SKILL.md
Scanned
2 files, 120 lines
Copies in repo
2 — 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 poletron-clerk-auth skill provides authentication capabilities using Clerk, a popular user authentication service. It allows AI agents to securely manage user logins and sessions, integrating with Clerk's API for features like email/password sign-in, social login (Google, GitHub), and multi-factor authentication. This skill streamlines the process of building secure applications powered by AI agents.

When to use it

  • Building a member portal: Authenticate users accessing exclusive content or services within an application.
  • Creating a collaborative workspace: Manage user access and permissions for shared projects and resources.
  • Developing a subscription-based service: Securely handle user accounts, payments, and entitlements.
  • Implementing secure data access: Control who can view and modify sensitive information based on their authentication status.

Key capabilities

  • User Authentication (Email/Password)
  • Social Login (Google, GitHub)
  • Multi-Factor Authentication Support
  • Session Management
  • Integration with Clerk API

Example prompts

  • "Authenticate this user with email '[email protected]' and password 'password'."
  • "Sign in the user using their Google account."
  • "Check if the current user is authenticated."

Tips & gotchas

  • Requires a Clerk API key to function correctly; ensure it’s securely provided to the agent.
  • Clerk's pricing and feature limitations may apply depending on your plan.