stripe-billing-subscriptions
Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/stripe-billing-subscriptions && cp -r /tmp/stripe-billing-subscriptions/examples/plugin-packages/stripe/skills/stripe-billing-subscriptions ~/.claude/skills/stripe-billing-subscriptionsSKILL.md
# 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.
Search and summarize material from the Acme research service.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.