Skip to content
TrustedSkillsbeta
Back to all skills

Clerk Webhooks

Checked
hookdeck·vlatest·security·MIT

Clerk Webhooks allows you to trigger actions in external apps (like Zapier or Make) based on Clerk events, streamlining workflows and automating processes.

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 hookdeck/webhook-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

hookdeck

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 hookdeck/webhook-skills at e9d1b145a4.

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

Commit
e9d1b145a4
Manifest
skills/clerk-webhooks/SKILL.md
Scanned
18 files, 2,019 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

clerk-webhooks

What it does

This skill enables AI agents to securely receive and process webhooks from Clerk, a user management platform. It allows agents to trigger automated workflows based on real-time events like user sign-ups, profile updates, or authentication status changes directly within your application logic.

When to use it

  • Automate onboarding sequences immediately after a new user registers via Clerk.
  • Trigger notifications or update internal databases when a user's email address changes.
  • Initiate specific actions in your app when a user successfully authenticates or logs out.
  • Monitor for critical security events, such as suspicious login attempts or account lockouts.

Key capabilities

  • Receives raw webhook payloads from Clerk's event system.
  • Parses standard Clerk event types including user.created, user.updated, and session.created.
  • Integrates with Hookdeck to manage delivery reliability and retry logic for webhooks.
  • Provides structured data access to user attributes contained in the webhook payload.

Example prompts

  • "Listen for a new user creation event from Clerk and send them a welcome email."
  • "Check if the latest webhook indicates a user has been locked out; if so, alert the support team."
  • "Update our internal CRM record whenever Clerk sends an update event regarding a user's profile picture change."

Tips & gotchas

Ensure your application has valid authentication credentials configured in Hookdeck to verify incoming requests from Clerk. Be mindful that webhook payloads contain sensitive user data; always sanitize inputs before processing them within your agent's logic.