Menu
Look up Stripe customers, subscriptions, charges, and payment methods. Cancel subscriptions and issue refunds. Use when investigating billing issues, subscription cancellations, or payment disputes.
| name | stripe |
| description | Look up Stripe customers, subscriptions, charges, and payment methods. Cancel subscriptions and issue refunds. Use when investigating billing issues, subscription cancellations, or payment disputes. |
| allowed-tools | Bash, Read |
Look up and manage Stripe customers, subscriptions, charges, and refunds for support investigations.
STRIPE_SECRET_KEY — from Stripe Dashboard > Developers > API Keys (Secret key)SKILL_DIR=".claude/skills/stripe"
# Look up a customer by email (shows subscriptions, charges, invoices)
node "$SKILL_DIR/query.mjs" customer user@example.com
# Search customers using Stripe Search syntax
node "$SKILL_DIR/query.mjs" search "email:'user@example.com'"
# Get subscription details
node "$SKILL_DIR/query.mjs" subscription sub_1ABC123
# List charges for a customer
node "$SKILL_DIR/query.mjs" charges user@example.com
# List payment methods
node "$SKILL_DIR/query.mjs" payment-methods user@example.com
# Cancel a subscription IMMEDIATELY
node "$SKILL_DIR/query.mjs" cancel sub_1ABC123
# Cancel at end of billing period
node "$SKILL_DIR/query.mjs" cancel sub_1ABC123 --at-period-end
# Refund a specific charge (full)
node "$SKILL_DIR/query.mjs" refund ch_1ABC123
# Partial refund (amount in cents)
node "$SKILL_DIR/query.mjs" refund ch_1ABC123 --amount 500
# Refund with reason
node "$SKILL_DIR/query.mjs" refund ch_1ABC123 --reason requested_by_customer
# Preview all refundable charges (dry run)
node "$SKILL_DIR/query.mjs" refund-all user@example.com --dry-run
# Refund ALL charges for a customer
node "$SKILL_DIR/query.mjs" refund-all user@example.com --reason requested_by_customer
| Command | Description |
|---|---|
customer <email> | Full customer lookup — details, subscriptions, charges, invoices |
search <query> | Search customers using Stripe Search syntax |
subscription <sub_xxx> | Get detailed subscription info |
charges <cus_xxx|email> | List charges for a customer |
payment-methods <cus_xxx|email> | List saved payment methods |
cancel <sub_xxx> | Cancel subscription immediately |
cancel <sub_xxx> --at-period-end | Cancel at end of current billing period |
refund <ch_xxx> | Full refund of a charge |
refund <ch_xxx> --amount <cents> | Partial refund |
refund-all <cus_xxx|email> | Refund all charges for a customer |
refund-all <cus_xxx|email> --dry-run | Preview refundable charges without refunding |
Valid --reason values:
duplicate — Charge was a duplicatefraudulent — Charge was fraudulentrequested_by_customer — Customer requested the refund| Flag | Description |
|---|---|
--json | Output raw JSON (useful for piping/processing) |
--at-period-end for graceful cancellation.--dry-run first to preview. Without --dry-run, it refunds every non-refunded charge.customer command is read-only and safe to run at any time.CustomerSubscription tableCheck civitai PROD deployment status across the live Tekton -> Flux -> Flagger chain on the DataPacket cluster (kubectl, read-only). Tekton/Flagger cluster state is the primary truth; the GitHub Deployments API is kept as a public cross-check. Use to see where a deploy is in the chain, watch it to completion, or debug a build/canary failure.
Run PostgreSQL queries for testing, debugging, and performance analysis. Use when you need to query the database directly, run EXPLAIN ANALYZE, compare query results, or test SQL optimizations. Always uses read-only connections unless explicitly directed otherwise.
Wire an existing ecosystem into the generation system. Adds generation support to basemodel.constants.ts, creates graph and handler files, and wires them into the ecosystem discriminator, workflow config, and router. Use after add-ecosystem when you need the ecosystem to show up in the generation form. Always checks @civitai/client for ecosystem-specific types before writing the handler.
Draft a model description for the CivitaiOfficial account when mirroring a third-party model on civitai.com or civitai.red. Use when the user is publishing or rewriting a mirrored model page (e.g. Sulphur, HappyHorse, Wan, ACE-Step) and wants a structured, properly-credited description rather than a one-line stub. Produces HTML ready to paste into the Civitai rich-text editor.
Read, replace, reset, export, and import XGuard policy options on the orchestrator. Use when you need to inspect current per-label policies for text or prompt scans, ship a refined policy, restore defaults, or back up the policy registry. Read-only by default; destructive operations require an explicit `--writable` flag.
Author a prompt-enhancement system prompt for a new ecosystem and register/update it on the orchestrator's prompt-analysis service. Use when onboarding a new ecosystem (e.g. happyhorse, a new Flux variant, a new Wan video version) and the user provides the ecosystem key plus a reference link, model card, or description. Produces a guide that mirrors the structure and tone of existing ecosystem guides so the prompt-analysis tool behaves consistently.