Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/integrating-stripe-webhooks
Use when implementing Stripe webhook endpoints and getting 'Raw body not available' or signature verification errors - provides raw body parsing solutions and subscription period field fixes across frameworks
Passed 22 of 22 test cases with the skill, and 18 of 22 without it.
and 3 more in the full report
4 fixed18 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact Stripe CLI command forwards incoming Stripe webhook events to a local development server running at http://localhost:3000/api/v1/webhooks/stripe?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the exact command stripe listen --forward-to localhost:3000/api/v1/webhooks/stripe | Missed | Passed |
The instructions your model reads when the skill loads.
Stripe webhooks require raw request bodies for signature verification. Most web frameworks parse JSON automatically, breaking verification. This skill provides framework-specific solutions for the raw body problem and documents common TypeScript type mismatches.
Use this skill when:
TypeError: Cannot read property 'current_period_start' from subscription eventsDon't use for:
| Problem | Solution |
|---|---|
| Raw body not available | Configure custom body parser (see framework examples) |
| Signature verification fails | Use raw body bytes/buffer, not parsed JSON |
| 404 on webhook endpoint | Register webhook route inside API prefix |
current_period_start undefined | Access from subscription.items.data[0] not root |
| URI validation errors | URL-encode dynamic parameters with encodeURIComponent() |
THE PROBLEM: Stripe's constructEvent() requires the exact bytes received to verify the signature. JSON parsing modifies the body, breaking verification.
THE SOLUTION: Access raw body before any parsing middleware.
Node.js - Fastify (most common for new projects):
test cases passed, vs 18 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.