What problem does it solve? Building Clerk webhook endpoints requires correct signature verification, raw-body parsing, public route configuration, and event payload handling — mistakes in any of these cause 401 errors, spoofed-event vulnerabilities, or missing database records. This Skill provides complete, verified webhook handler patterns so events like user signups and organization changes reliably sync to your database, email, and Slack. ## Core Features & Use Cases - Signature-Verified Handlers: Generates handlers using verifyWebhook from framework-specific packages (@clerk/nextjs/webhooks, @clerk/express/webhooks, etc.) that read CLERK_WEBHOOK_SIGNING_SECRET automatically. - Full Event Catalog Coverage: Handles user, session, organization, organization membership, billing/subscription, and payment events with typed payload field references. - Framework-Specific Guidance: Includes per-framework examples for Next.js, Express, Astro, Fastify, Nuxt, React Router, and TanStack Start, plus a troubleshooting table for common failures like 401s and Express body-parsing issues. - Use Case: When a user signs up, automatically create a row in your Postgres users table via Prisma, send a welcome email through Resend, and post a notification to your Slack channel — all from one verified webhook handler. ## Quick Start Ask the assistant to set up a Clerk webhook handler in your Next.js app that verifies the signature and creates a database record whenever a user.created event fires.