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.
88
81%
Does it follow best practices?
Impact
100%
1.47xAverage score across 3 eval scenarios
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-crafted skill description that excels at trigger term quality and completeness with explicit 'Use when' guidance and specific Clerk event names. The main weakness is that the capability description could be more comprehensive, listing additional specific actions beyond just 'receive and verify'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk webhooks) and two actions (receive, verify), but doesn't comprehensively list specific capabilities like parsing payloads, handling retries, or configuring endpoints. | 2 / 3 |
Completeness | Clearly answers both what ('Receive and verify Clerk webhooks') and when ('Use when setting up Clerk webhook handlers, debugging signature verification, or handling user events...') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Clerk webhooks', 'webhook handlers', 'signature verification', and specific event names like 'user.created', 'user.updated', 'session.created', 'organization.created'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Clerk-specific terminology and event names. Unlikely to conflict with generic webhook skills or other authentication provider skills due to explicit Clerk branding. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 webhook skill with excellent actionability through complete, executable code examples for multiple frameworks. The progressive disclosure is well-structured with clear navigation to additional resources. However, it could be more concise by trimming the extensive related skills list, and would benefit from explicit workflow steps for the full setup-to-production process.
Suggestions
Add an explicit numbered workflow for end-to-end setup: 1) Create endpoint in Clerk Dashboard, 2) Copy signing secret, 3) Implement handler, 4) Test with Hookdeck, 5) Verify events are received
Trim or remove the 'Related Skills' section - listing 10+ other skills adds token overhead without helping Claude execute this specific task
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary content like the extensive 'Related Skills' section listing 10+ other skills, and the attribution section which adds little value for Claude's task execution. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for both Express and FastAPI implementations. Includes complete webhook handlers with signature verification, header extraction, and event handling switch statements. | 3 / 3 |
Workflow Clarity | The code examples show the verification flow implicitly, but there's no explicit step-by-step workflow for setting up webhooks end-to-end. Missing explicit validation checkpoints like 'test your endpoint before going live' or debugging steps when verification fails. | 2 / 3 |
Progressive Disclosure | Excellent structure with quick-start code inline, clear references to example directories and reference materials, and well-organized sections. References are one level deep and clearly signaled with descriptive links. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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.
f8a4801
Table of Contents
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.