Skip to content
TrustedSkillsbeta
Back to all skills

Clerk Webhooks

Official
clerk·vlatest·security

Clerk Webhooks allows you to trigger actions in external services (like Slack or Zapier) based on changes within your Clerk database, streamlining workflows and automating tasks.

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 clerk/skills --skill clerk-webhooks -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

clerk

Matched to the vendor's own GitHub organisation.

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 clerk/skills at 863ff165de.

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

Commit
863ff165de
Manifest
skills/features/clerk-webhooks/SKILL.md
Scanned
3 files, 591 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 clerk-webhooks skill enables integration with Clerk's webhook system, allowing AI agents to receive and process real-time events from Clerk services. This includes user authentication actions, session management updates, and other relevant triggers that occur within the Clerk ecosystem.

When to use it

  • When you need to react in real time to user sign-ups or logins via Clerk.
  • To automate workflows based on changes in user data or session status.
  • For monitoring and responding to events like failed login attempts or account creations.

Key capabilities

  • Real-time event listening from Clerk services
  • Processing of authentication-related webhooks (e.g., user created, session created)
  • Integration with AI agents for automated responses or actions based on webhook data

Example prompts

  • "Notify me when a new user signs up through Clerk."
  • "Trigger an action whenever a user logs in successfully."
  • "Log all failed login attempts from Clerk into a dashboard."

Tips & gotchas

  • Ensure your Clerk instance is configured to send webhooks to the correct endpoint.
  • Handle webhook payloads securely and validate their authenticity to prevent spoofing.