Skip to content
Skills Library
Finance & accounting · Tool integration

stripe-operator

/stripe-operator

Inspect and operate Stripe (customers, payments, subscriptions, invoices, products) through the Stripe API or CLI. Use for billing questions, payment debugging, and revenue reporting.

Repository
navin ↗
Licence
AGPL-3.0
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Inspect and operate Stripe (customers, payments, subscriptions, invoices, products) through the Stripe API or CLI. Use for billing questions, payment debugging, and revenue reporting.

Original author description

Inspect and operate Stripe (customers, payments, subscriptions, invoices, products) through the Stripe API or CLI. Use for billing questions, payment debugging, and revenue reporting.

How it works

  1. When to use
  2. Access
  3. Workflow
  4. Guardrails
Original SKILL.md headings · 38 lines, 230 words
SKILL.md preview
---
name: stripe-operator
description: Inspect and operate Stripe (customers, payments, subscriptions, invoices, products) through the Stripe API or CLI. Use for billing questions, payment debugging, and revenue reporting.
metadata: {"navin":{"emoji":"💳","category":"data","requires":{"env":["STRIPE_API_KEY"]}}}
---

# 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):

```bash
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

1. Clarify the question (which object, which period, live or test mode - test keys start with `sk_test_`).
2. Query read endpoints first; paginate with `starting_after` when needed.
3. Aggregate locally (jq/python) for reports: MRR, churn, failed payments by reason.
4. For mutations (refunds, cancellations, coupon creation), show the exact call and ask for confirmation before executing.
5. 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.

Versions

The database has no other skills named stripe-operator.

Database snapshot: 13.11.2026 · package version 46a944c2ef77 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100stripe
    Read and write customers, charges, payment intents, invoices, subscriptions and refunds in your Stripe account via the Stripe API. Use when the user asks about payments, revenue, a customer's billing, a failed charge, an invoice, or a subscription.
  • 90stripe
    Stripe API integration with managed OAuth. Manage customers, subscriptions, invoices, products, prices, and payments. Use this skill when users want to process payments, manage billing, or handle subscriptions with Stripe. For other third party apps, use the api-gateway skill…
  • 90stripe
    Stripe API integration with managed OAuth. Manage customers, subscriptions, invoices, products, prices, and payments. Use this skill when users want to process payments, manage billing, or handle subscriptions with Stripe. For other third party apps, use the api-gateway skill…
  • 95Stripe
    Runs Stripe billing operations via the Stripe SDK and, when configured, an admin dashboard's cached endpoints: products, prices, subscriptions, MRR and revenue, customers, payments, refunds, coupons, disputes. USE WHEN Stripe, subscriptions, billing, MRR, revenue, customers,…
  • 100stripe-operations
    Operate Stripe safely from an agent or VPS: verify access, install/use Stripe CLI, inspect products/prices/customers/subscriptions/checkout sessions/webhooks, and perform guarded payment operations. Use when the user asks about Stripe access, Stripe CLI setup, billing audits,…
  • 100int-stripe
    Query and manage Stripe data via the Stripe API. Use when you need to list charges, customers, invoices, subscriptions, payment intents, refunds, products, or prices. Supports filtering, pagination, and creating/updating customers and refunds. Calls api.stripe.com directly with no third-party proxy.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.