Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add Devin-AXIS/iPolloWork --skill stripe-billing-subscriptions --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Stripe Billing Subscriptions?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/devin-axis-stripe-billing-subscriptions)More formats (shields.io, HTML) on the badges page.
---
name: stripe-billing-subscriptions
description: Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.
disable-model-invocation: false
---
# Stripe Billing And Subscriptions
1. Confirm test or live mode and resolve the exact customer or subscription.
2. Read the current subscription, items, prices, invoices, payment state, trial, cancellation, and collection settings relevant to the request.
3. Explain current state and the expected effect of a proposed change, including timing and proration when evidence is available.
4. Preview changes to plan, quantity, cancellation, trial, or collection behavior before writing.
5. Re-read affected objects after a confirmed write.
Do not guess prices, tax behavior, billing-cycle anchors, or proration outcomes.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...