Stripe Operator
Operate a Stripe account safely: read-first, confirm before any mutating call.
When to use
- The user asks about customers, payments, subscriptions, invoices, refunds, or products in Stripe.
- Debugging a failed payment or webhook.
- Building a revenue/billing report.
Access
Use the REST API with the STRIPE_API_KEY environment variable (never print the key):
curl -s https://api.stripe.com/v1/customers?limit=10 -u "$STRIPE_API_KEY:" | jq '.data[] | {id, email, created}'
curl -s "https://api.stripe.com/v1/payment_intents?limit=20" -u "$STRIPE_API_KEY:" | jq '.data[] | {id, amount, currency, status}'
curl -s "https://api.stripe.com/v1/subscriptions?status=active&limit=20" -u "$STRIPE_API_KEY:" | jq '.data[] | {id, customer, status, current_period_end}'
curl -s "https://api.stripe.com/v1/invoices?limit=10" -u "$STRIPE_API_KEY:" | jq '.data[] | {id, customer, amount_due, status}'
If the stripe CLI is installed, prefer it for logs and webhook testing: stripe listen, stripe trigger payment_intent.succeeded, stripe logs tail.
Workflow
- Clarify the question (which object, which period, live or test mode - test keys start with
sk_test_).
- Query read endpoints first; paginate with
starting_after when needed.
- Aggregate locally (jq/python) for reports: MRR, churn, failed payments by reason.
- For mutations (refunds, cancellations, coupon creation), show the exact call and ask for confirmation before executing.
- Summarize amounts with currency and mode (test/live) clearly labeled.
Guardrails
- Never create charges or refunds without explicit user confirmation.
- Never log or echo the API key.
- Flag when operating on live mode data.
1---2name: stripe-operator3description: Inspect and operate Stripe (customers, payments, subscriptions, invoices, products) through the Stripe API or CLI. Use for billing questions, payment debugging, and revenue reporting.4metadata:5 source: https://skillmd.com/skills/navinspire-ia/stripe-operator6 navin:7 emoji: 💳8 category: data9 requires:10 env:11 - STRIPE_API_KEY12---1314# Stripe Operator1516Operate a Stripe account safely: read-first, confirm before any mutating call.1718## When to use1920- The user asks about customers, payments, subscriptions, invoices, refunds, or products in Stripe.21- Debugging a failed payment or webhook.22- Building a revenue/billing report.2324## Access2526Use the REST API with the `STRIPE_API_KEY` environment variable (never print the key):2728```bash29curl -s https://api.stripe.com/v1/customers?limit=10 -u "$STRIPE_API_KEY:" | jq '.data[] | {id, email, created}'30curl -s "https://api.stripe.com/v1/payment_intents?limit=20" -u "$STRIPE_API_KEY:" | jq '.data[] | {id, amount, currency, status}'31curl -s "https://api.stripe.com/v1/subscriptions?status=active&limit=20" -u "$STRIPE_API_KEY:" | jq '.data[] | {id, customer, status, current_period_end}'32curl -s "https://api.stripe.com/v1/invoices?limit=10" -u "$STRIPE_API_KEY:" | jq '.data[] | {id, customer, amount_due, status}'33```3435If the `stripe` CLI is installed, prefer it for logs and webhook testing: `stripe listen`, `stripe trigger payment_intent.succeeded`, `stripe logs tail`.3637## Workflow38391. Clarify the question (which object, which period, live or test mode - test keys start with `sk_test_`).402. Query read endpoints first; paginate with `starting_after` when needed.413. Aggregate locally (jq/python) for reports: MRR, churn, failed payments by reason.424. For mutations (refunds, cancellations, coupon creation), show the exact call and ask for confirmation before executing.435. Summarize amounts with currency and mode (test/live) clearly labeled.4445## Guardrails4647- Never create charges or refunds without explicit user confirmation.48- Never log or echo the API key.49- Flag when operating on live mode data.