clerk-webhooks-events
Configure Clerk webhooks and handle authentication events. Use when setting up user sync, handling auth events, or integrating Clerk with external systems via Svix webhooks. Trigger with phrases like "clerk webhooks", "clerk events", "clerk user sync", "clerk svix", "clerk event handling".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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 well-structured skill description with strong trigger terms, explicit 'Use when' guidance, and a clear niche. Its main weakness is that the capability description could be more specific about the concrete actions performed (e.g., endpoint setup, signature verification, specific event types). Overall it's a solid description that would perform well in skill selection.
Suggestions
Add more specific concrete actions like 'set up webhook endpoints, verify Svix signatures, parse user.created/user.updated events, sync user data to databases' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk webhooks, authentication events) and some actions (configure, handle, sync), but doesn't list multiple specific concrete actions like endpoint setup, event parsing, signature verification, or specific event types handled. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Clerk webhooks, handle authentication events) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Trigger with phrases' section listing exact trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'clerk webhooks', 'clerk events', 'clerk user sync', 'clerk svix', 'clerk event handling', plus mentions of 'auth events' and 'Svix webhooks' — these are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Clerk-specific webhook configuration with Svix is highly specific and unlikely to conflict with generic webhook or authentication skills. The combination of Clerk + webhooks + Svix creates a clear, unique identity. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent executable code examples and clear workflow sequencing. Its main weakness is length — the skill tries to cover multiple frameworks (Next.js and Express), two verification approaches, idempotency, and enterprise considerations all inline, which hurts conciseness and progressive disclosure. The critical gotchas and error handling table add significant practical value.
Suggestions
Extract the Express.js endpoint (Step 6) and idempotency implementation (Step 4) into separate bundle files, referencing them from the main SKILL.md to improve progressive disclosure and reduce inline length.
Remove the overview explanation of Svix and HMAC-SHA256 — Claude already knows these concepts. Start directly with prerequisites or the quick start.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy (e.g., both verifyWebhook and manual Svix approaches are fully spelled out, user.created and user.updated handlers share nearly identical code). The overview sentence explaining what Svix is and what HMAC-SHA256 means is unnecessary for Claude. However, most content earns its place with concrete, non-obvious implementation details like the req.text() vs req.json() gotcha. | 2 / 3 |
Actionability | Excellent actionability — every step includes fully executable TypeScript code with proper imports, type annotations, and real API calls. The code covers Next.js App Router, Express.js, idempotency patterns, and event handling with copy-paste-ready examples. Critical gotchas (req.text() vs req.json(), express.raw()) are clearly called out. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced from installation through endpoint creation, event handling, idempotency protection, dashboard configuration, and local testing. Validation is embedded throughout — signature verification acts as the primary checkpoint, idempotency handles retries, and the error handling table provides a clear troubleshooting feedback loop. The 'CRITICAL' annotations highlight common failure points. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical flow, but it's quite long (~200+ lines of code) with no bundle files to offload detail into. The Express.js alternative, idempotency implementation, and enterprise considerations could be split into separate reference files. The external resource links at the end are helpful but the inline content itself could benefit from better separation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
09b10d6
- Reviewed
Table of Contents
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.