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.
96
93%
Does it follow best practices?
Impact
100%
1.31xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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 follows best practices. It uses third person voice, provides specific concrete actions, includes a clear 'Use when...' clause with multiple trigger scenarios, and lists specific Stripe event names that developers would naturally reference. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Receive and verify Stripe webhooks', 'setting up Stripe webhook handlers', 'debugging signature verification', and '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', plus specific event names that developers would search for. These are terms developers naturally use when working with Stripe integrations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around Stripe webhooks specifically. The mention of Stripe-specific concepts (signature verification, specific event names) makes it unlikely to conflict with generic webhook skills or other payment processor skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and conciseness. The code examples are production-ready and the progressive disclosure is well-executed with clear references to detailed materials. The main weakness is the lack of an explicit setup workflow with validation steps to confirm the webhook integration is working.
Suggestions
Add a numbered setup workflow (e.g., 1. Add endpoint, 2. Configure in Stripe dashboard, 3. Test with CLI, 4. Verify event received) with explicit validation checkpoints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing essential code without explaining what Stripe or webhooks are. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code for both Express and FastAPI. Includes specific environment variables, CLI commands for local testing, and a clear event type reference table. | 3 / 3 |
Workflow Clarity | The code examples show the verification-then-handle pattern, but there's no explicit workflow sequence for setting up webhooks end-to-end. Missing validation checkpoints for testing that the webhook is working correctly after setup. | 2 / 3 |
Progressive Disclosure | Excellent structure with quick-start code inline and clear one-level-deep references to examples/, references/, and external documentation. Navigation is well-signaled with descriptive links. | 3 / 3 |
Total | 11 / 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.
- Repository
- hookdeck/webhook-skills
- Commit
f8a4801
- 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.