clerk-webhooks

Receive and verify Clerk webhooks. Use when setting up Clerk webhook handlers, debugging signature verification, or handling user events like user.created, user.updated, session.created, or organization.created.

Quality

86%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with excellent executable code examples for two languages and good progressive disclosure to reference materials. The main weaknesses are the verbose Related Skills section (10 links) and Attribution boilerplate that consume tokens without adding instructional value, plus a lack of explicit step-by-step setup workflow connecting the Dashboard configuration to code deployment.

Suggestions

Remove or significantly trim the Related Skills section — listing 10 sibling skills adds little value and wastes tokens.

Add a brief numbered setup workflow (e.g., 1. Install package → 2. Set env var → 3. Add endpoint in Dashboard → 4. Test with tunnel) to tie the scattered sections into a clear sequence.

Remove the Attribution section — this is boilerplate that doesn't help Claude perform the task.

Dimension	Reasoning	Score
Conciseness	The core code examples are well-structured and necessary, but the Related Skills section listing 10 other skills is excessive padding. The Attribution section and some explanatory comments (e.g., explaining what Standard Webhooks is) add tokens without much value. The recommended webhook-handler-patterns section with 4 external links is also verbose.	2 / 3
Actionability	Provides fully executable, copy-paste ready code for both Express and FastAPI. Includes critical details like express.raw() requirement, header mapping from svix-* to webhook-*, secret format validation, timestamp checking, and environment variable names. The local development tunnel command is also immediately actionable.	3 / 3
Workflow Clarity	The code examples implicitly contain a workflow (verify → parse → handle), and there are validation steps within the code (header checks, signature verification, timestamp window). However, there's no explicit sequenced workflow for setup (e.g., 1. Install package, 2. Set env vars, 3. Create endpoint, 4. Configure dashboard, 5. Test with tunnel). The setup process across Dashboard, env vars, and local dev is scattered across sections without clear sequencing.	2 / 3
Progressive Disclosure	The SKILL.md provides a clear overview with essential code inline, then points to one-level-deep references (references/overview.md, references/setup.md, etc.) and examples (examples/express/, examples/nextjs/, examples/fastapi/). Navigation is well-signaled with descriptive labels for each reference file.	3 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates its purpose, uses third-person voice, and includes an explicit 'Use when' clause with highly specific trigger terms. The enumeration of specific Clerk event types (user.created, session.created, etc.) makes it both easy to match and clearly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Receive and verify Clerk webhooks', and enumerates specific event types like 'user.created', 'user.updated', 'session.created', 'organization.created'. Also mentions 'signature verification' and 'webhook handlers' as concrete capabilities.	3 / 3
Completeness	Clearly answers both 'what' (receive and verify Clerk webhooks) and 'when' (explicit 'Use when' clause covering setup, debugging signature verification, and handling specific user events). The trigger guidance is explicit and well-structured.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Clerk webhooks', 'webhook handlers', 'signature verification', 'user.created', 'user.updated', 'session.created', 'organization.created', 'user events'. These are the exact terms developers would use when seeking help with Clerk webhook integration.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — specifically scoped to Clerk webhooks with named event types. Unlikely to conflict with generic webhook skills or other authentication provider skills due to the explicit 'Clerk' branding and specific event names.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: hookdeck/webhook-skills
Commit: da37fc7

Reviewed: 18 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.