CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

83%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 workflow clarity and practical, executable code examples covering multiple frameworks and edge cases. Its main weakness is length—the comprehensive coverage of both verification approaches, multiple frameworks, and idempotency could be better organized through progressive disclosure into supporting files. Minor verbosity in explanatory text could be trimmed.

Suggestions

Extract the Express.js endpoint and manual Svix verification into separate referenced files to reduce the main SKILL.md length and improve progressive disclosure.

Trim the overview paragraph—Claude doesn't need to be told what HMAC-SHA256 is or that Clerk uses Svix; jump straight to the actionable content.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some redundancy—the user.updated handler largely duplicates user.created, and both the verifyWebhook and manual Svix approaches are shown in full when the alternative could be more condensed. The overview sentence explaining what Svix is and what HMAC-SHA256 means is unnecessary for Claude. However, most content earns its place with critical gotchas (req.text() vs req.json()) and practical code.

2 / 3

Actionability

The skill provides fully executable, copy-paste-ready TypeScript code for both Next.js and Express.js, complete with imports, error handling, and database operations. Critical pitfalls are called out inline (e.g., 'Use req.text(), NOT req.json()'). The error handling table and dashboard configuration steps are concrete and specific.

3 / 3

Workflow Clarity

The steps are clearly numbered and 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 handling addresses retry scenarios, and the error handling table provides a feedback loop for common failures.

3 / 3

Progressive Disclosure

The content is well-structured with clear sections and a helpful error table, but it's quite long (~200+ lines of code) and could benefit from splitting the alternative approaches (Express.js, manual Svix) and the idempotency module into separate referenced files. The external resource links at the bottom are good, but there are no bundle files to offload detailed content to. The reference to 'clerk-performance-tuning' is a nice forward pointer.

2 / 3

Total

10

/

12

Passed

Description

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 excellent trigger term coverage and clear 'what/when' guidance. Its main weakness is that the capability description could be more specific about the concrete actions performed (e.g., verifying webhook signatures, handling specific event types like user.created). Overall it's a strong description that would perform well in skill selection.

Suggestions

Add more specific concrete actions like 'verify webhook signatures', 'handle user.created/user.updated events', or 'configure webhook endpoints' to improve specificity.

DimensionReasoningScore

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' (setting up user sync, handling auth events, integrating Clerk with external systems via Svix webhooks), with explicit trigger phrases provided.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms including 'clerk webhooks', 'clerk events', 'clerk user sync', 'clerk svix', 'clerk event handling' — these are terms users would naturally use when needing this skill, and the explicit listing of trigger phrases is very helpful.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — the combination of Clerk, Svix, webhooks, and authentication events creates a very specific niche that is unlikely to conflict with other skills. The trigger terms are all Clerk-specific.

3 / 3

Total

11

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.