stripe_skill

This skill audits, fixes, and verifies Stripe integration end-to-end, ensuring checkout flows work and subscriptions stay in sync on every run.
  • Python

4

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill phrazzld/claude-config --skill stripe

  • SKILL.md5.9 KB

Overview

This skill performs complete Stripe lifecycle management: it audits your integration, fixes all issues, and verifies checkout and webhook flows end-to-end on every run. It enforces environment parity, subscription UX, security, and business-model constraints, then validates with real test checkouts and webhook deliveries.

How this skill works

The skill first detects environment mismatches between your app and Stripe CLI profiles to avoid invisible resources. It runs a deep automated audit across configuration, webhooks, subscription logic, security, and UX. From findings it builds a prioritized remediation plan, applies configuration fixes directly and delegates code fixes to an automated coder flow, then runs full verification using test checkout sessions and webhook delivery checks.

When to use it

  • When repository references stripe package, STRIPE_* env vars, or webhook handlers are modified
  • If checkouts fail, webhooks are missing or pending, or subscriptions behave unexpectedly
  • Before shipping changes that touch billing, subscription access control, or payment flows
  • When onboarding a new account or migrating CLI profile to avoid environment mismatch
  • When subscription management UX or billing history is missing or incomplete

Best practices

  • Detect and fix environment mismatches before any Stripe operations (CLI profile vs app keys)
  • Treat every run as full audit → plan → execute → verify; don’t stop at a report
  • Prioritize fixes: Critical (checkout blocks) → High (security/data) → Medium (UX)
  • Keep secrets out of code, verify webhook signature checks, and ensure idempotency
  • Verify with real test sessions (card 4242...) and confirm webhook pending_webhooks = 0

Example use cases

  • Add or repair webhook handlers and ensure Stripe dashboard endpoints point to canonical URLs
  • Fix missing or inconsistent STRIPE_SECRET_KEY across dev and prod deployments
  • Implement subscription settings page with billing history, payment method display, and Portal integration
  • Resolve failed checkouts by correcting API usage, idempotency, and subscription trial logic
  • Validate a migration to a new Stripe account or CLI profile without losing visibility

FAQ

Yes—configuration fixes are applied directly. Code fixes are executed via a controlled Codex flow with explicit specs and verification steps; code changes are committed on a feature branch.

How are webhooks verified?

The skill checks Stripe webhook endpoints, ensures POST returns non-3xx, validates pending_webhooks = 0, and performs signature verification tests using test events.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
stripe skill by phrazzld/claude-config | VeilStrat