Stripe Operations

Use this skill to read Stripe account state and, with explicit confirmation, perform guarded mutations: account balance, payment intents, subscriptions, and subscription cancellation. This is a tool skill for the Stripe platform. Building Stripe payments into an application is integration development; this skill owns the everyday agent workflow: answering "what is our balance?", "which payments succeeded?", "what subscriptions are active?", and applying a confirmed cancellation.

Operating contract

1. Read-only first. Balance, payment, and subscription queries run freely and never change anything. The bundled stripe-cli script's primary surface is these reads.
2. Guard every mutation. State-changing operations — canceling a subscription — require an explicit human directive plus --dry-run preview and --yes confirmation through stripe-cli. Cancellations are financial actions with billing consequences: confirm the subscription, the timing, and the impact before acting.
3. Respect bounded reads. Stripe paginates with limit and has_more; never page past what the task needs. stripe-cli --limit caps every listing.
4. Keep evidence bounded. Quote short IDs, amounts, and statuses; never dump full API keys, customer data, or raw payloads into chat.
5. Treat money data as sensitive. Balances, payments, and subscription details are financial records; quote only what the question needs and never expose full card or customer data.

The stripe-cli script

scripts/stripe-cli is an agent-first, stdlib-only CLI over the Stripe API. It is read-only-first: balance, payments, and subscriptions are the primary surface; the only mutation is guarded.