creating-webhook-handlers

Create webhook endpoints with signature verification, retry logic, and payload validation. Use when receiving and processing webhook events. Trigger with phrases like "create webhook", "handle webhook events", or "setup webhook handler".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

85%Weight 40%Scale 1-3

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

The body is a well-structured, concise overview with a clear sequenced workflow, explicit verification, and well-signaled one-level-deep references. Its only weakness is actionability: the body itself lacks executable code blocks, delegating them to reference files.

Suggestions

Add a short copy-paste-ready signature-verification code snippet (or an inline HMAC verify example) directly in the Instructions so the body is executable without opening references.

Convert the ${CLAUDE_SKILL_DIR}/references/*.md path tokens to relative markdown links (e.g., [implementation.md](references/implementation.md)) for cleaner, click-navigable progressive disclosure.

Optionally inline a minimal idempotency-check code snippet alongside step 4 to lift actionability from concrete guidance to fully executable.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview that delegates detail to reference files and does not explain concepts Claude already knows, so every section earns its place rather than padding as in the level-2 example.	3 / 3
Actionability	Guidance is concrete (specific headers like Stripe-Signature, status codes, idempotency keys) but the body contains no executable code/commands block; copy-paste-ready code lives in referenced files, fitting the level-2 "concrete but incomplete / pseudocode-over-executable" anchor rather than level 3.	2 / 3
Workflow Clarity	Eight clearly sequenced steps include explicit validation (signature verification before responding, idempotency check) and a verification step (replay tests with tampered signatures), plus feedback loops in the Error Handling table, matching the level-3 anchor.	3 / 3
Progressive Disclosure	The overview splits detail into three one-level-deep, clearly signaled reference files (implementation.md, errors.md, examples.md) that all resolve on disk, matching the well-organized level-3 anchor rather than the inline-dump level-2 example.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is specific, complete, and distinctive, naming concrete capabilities and providing explicit trigger guidance with natural user phrasings. It cleanly satisfies the highest anchor on every dimension.

Dimension	Reasoning	Score
Specificity	"Create webhook endpoints with signature verification, retry logic, and payload validation" lists multiple specific concrete actions, matching the level-3 anchor rather than the partial naming of level 2.	3 / 3
Completeness	It clearly answers what (signature verification, retry logic, payload validation) and provides an explicit "Use when receiving and processing webhook events" trigger, satisfying both halves required for level 3.	3 / 3
Trigger Term Quality	Explicit trigger phrases ("create webhook", "handle webhook events", "setup webhook handler") are natural terms a user would say, giving good coverage rather than the missing-variations profile of level 2.	3 / 3
Distinctiveness Conflict Risk	Webhook endpoint handling with these distinct triggers is a clear niche unlikely to conflict with other skills, fitting the level-3 anchor rather than the overlapping level-2 example.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/api-development/webhook-handler-creator/skills/creating-webhook-handlers/SKILL.md
Commit: 4c47e33

Reviewed: 3 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.