stripe

Stripe

Use this skill for Stripe Dashboard, Stripe API, Stripe CLI, and integration-debugging workflows.

Scope

• investigate customers, products, prices, payments, checkout sessions, and subscriptions
• debug webhook delivery and local webhook forwarding
• inspect or use the Stripe API through an existing authenticated integration
• coordinate Dashboard actions through the browser when the user is already signed in
• draft safe operational steps for Stripe-backed app changes

Default Strategy

1. Confirm whether the task is in test mode or live mode.
2. Prefer read-only inspection before any mutation.
3. Use Stripe CLI or an existing API client when a terminal or application workflow is available; otherwise use the Dashboard in the browser.
4. Confirm the exact object id or customer email before changing anything.

Stripe CLI

Basic checks:

stripe version
stripe login
stripe config --list

Useful read commands:

stripe customers list --limit 10
stripe customers retrieve cus_123
stripe products list --limit 20
stripe prices list --product prod_123
stripe subscriptions retrieve sub_123
stripe payment_intents retrieve pi_123
stripe events list --limit 10

Stripe API

Use the API when the application already has a configured Stripe client, authenticated helper, or server-side integration path.

Prefer the official Stripe SDKs over ad hoc HTTP calls when you are working in application code. Useful read-first targets include:

• /v1/customers/{id}
• /v1/subscriptions/{id}
• /v1/payment_intents/{id}
• /v1/checkout/sessions/{id}
• /v1/events/{id}
• /v1/prices?product={product_id}

For API-backed debugging:

1. confirm whether the request is against test or live mode
2. trace one concrete object id end to end
3. compare the API object state with webhook delivery and app logs
4. mutate only after the read path is understood

If the user wants integration help, state whether the source of truth is:

• Stripe API
• Stripe CLI
• Dashboard
• application logs