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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

75%Weight 40%Scale 1-5

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

A well-organized, actionable overview that leads with executable verification code and offloads detail to reference files. Main gaps are references to example directories that don't exist in the bundle and a missing explicit request/response feedback loop around the verify step.

Suggestions

Either include the examples/express, examples/nextjs, and examples/fastapi directories in the bundle or remove/descope those links so every referenced path resolves.

Add an explicit feedback checkpoint after verification (e.g. 'On SignatureVerificationError, respond 400 and log; do not process the event') to close the receive→verify→handle loop.

Trim the 10-item Related Skills list to the 2-3 most relevant to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — inline-commented Node/Python snippets, a compact event table, and terse env/local-dev sections — with only mild padding from the 10-item Related Skills list and the promotional Recommended section.	4 / 5
Actionability	The core verification code (constructEvent / construct_event with raw body, signature, secret) is concrete and copy-paste ready, but full route-wired handlers are delegated to example directories rather than shown inline.	4 / 5
Workflow Clarity	The verify step is unambiguous with explicit error behavior ('Throws/Raises SignatureVerificationError on tampering or stale timestamp'), but the broader receive→verify→handle sequence is only implied and lacks an explicit validate-and-respond checkpoint.	4 / 5
Progressive Disclosure	Good section structure with one-level-deep references to the real references/*.md files, but the body also points to examples/express\|nextjs\|fastapi/ directories that are not present in the bundle, a minor navigation gap.	4 / 5
	Total	16 / 20 Passed

Description

90%Weight 40%Scale 1-5

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

A strong, third-person description that clearly states the capability and provides explicit, natural 'Use when' triggers with concrete event examples. The only weakness is that it names just two capability actions, slightly understating the full range of what the skill supports.

Suggestions

Add one or two more capability verbs (e.g. '...parse, and dispatch Stripe webhooks') to lift specificity from naming 2 actions to a more comprehensive action list.

Consider mentioning idempotent event handling or retry behavior in the description to better distinguish the skill's full scope from mere signature verification.

Dimension	Reasoning	Score
Specificity	Names the domain ('Stripe webhooks') and two concrete actions ('Receive and verify'), matching the anchor for 1-2 concrete actions without comprehensive coverage; the event names that follow are trigger scenarios, not additional capability actions.	3 / 5
Completeness	Explicitly answers both what ('Receive and verify Stripe webhooks') and when ('Use when setting up... debugging... or handling payment events like...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say — 'setting up Stripe webhook handlers', 'debugging signature verification', and concrete event names like 'payment_intent.succeeded' — giving broad keyword coverage.	5 / 5
Distinctiveness Conflict Risk	Clear Stripe-webhook niche with provider-specific triggers and event names, making overlap with other skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: hookdeck/webhook-skills
Path: skills/stripe-webhooks/SKILL.md
Commit: daaf3db

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