stripe-webhooks

Receive and verify Stripe webhooks. Use when setting up Stripe webhook handlers, debugging signature verification, or handling payment events like payment_intent.succeeded, customer.subscription.created, or invoice.paid.

Quality

82%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

64%

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

The skill excels at actionability with clean, executable code examples for signature verification in two languages. However, it suffers from bloat in the Related Skills and Recommended sections, lacks a clear end-to-end workflow sequence, and references files that cannot be verified. Trimming the promotional content and adding a numbered setup workflow would significantly improve it.

Suggestions

Add a numbered end-to-end workflow: 1. Configure env vars → 2. Create route → 3. Verify signature → 4. Dispatch event → 5. Return 200/error, with a validation checkpoint after verification.

Trim the 'Related Skills' section to 2-3 most relevant skills or remove entirely — it consumes significant tokens without adding actionable guidance.

Merge the 'Recommended: webhook-handler-patterns' section into the Reference Materials section as a single line to reduce redundancy with Related Skills.

Dimension	Reasoning	Score
Conciseness	The core verification section is lean and efficient, but the 'Related Skills' section is excessively long (10 items with full URLs), the 'When to Use This Skill' section restates the description, and the Attribution section adds tokens for a non-essential concern. The recommended skill section also duplicates the related skills listing.	2 / 3
Actionability	Provides fully executable code examples for both Node and Python with clear comments, specific environment variable names, and a concrete local development command. The code is copy-paste ready with proper SDK method calls and error types documented inline.	3 / 3
Workflow Clarity	The verification step is clear, but there's no explicit workflow sequence for setting up a complete webhook handler (e.g., 1. Set env vars, 2. Create endpoint, 3. Verify signature, 4. Handle event, 5. Return 200). The skill defers full handler examples to example directories without providing the core sequence inline. No validation/verification checkpoint for testing the setup.	2 / 3
Progressive Disclosure	References to examples/ directories and references/ files are well-signaled, but no bundle files were provided to verify these exist. The Related Skills section is an overwhelming list that could be trimmed. The split between core content and references is reasonable, but the inline content could better summarize what each reference contains.	2 / 3
	Total	9 / 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 an excellent skill description that clearly communicates what the skill does and when to use it. It uses third person voice, includes specific Stripe event names as trigger terms, and has an explicit 'Use when' clause covering multiple scenarios. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Receive and verify Stripe webhooks', 'setting up Stripe webhook handlers', 'debugging signature verification', 'handling payment events' with specific event names like 'payment_intent.succeeded', 'customer.subscription.created', 'invoice.paid'.	3 / 3
Completeness	Clearly answers both what ('Receive and verify Stripe webhooks') and when ('Use when setting up Stripe webhook handlers, debugging signature verification, or handling payment events...') with explicit trigger scenarios and specific event examples.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Stripe webhooks', 'webhook handlers', 'signature verification', 'payment events', and specific event names like 'payment_intent.succeeded', 'customer.subscription.created', 'invoice.paid'. These are exactly the terms a developer would use when seeking help with Stripe webhook integration.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Stripe webhook handling specifically. The mention of Stripe-specific event names and signature verification makes it very unlikely to conflict with other skills, even other payment or API-related skills.	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.