stripe-payment-investigation
Investigate Stripe payment failures and unexpected outcomes from exact object IDs, lifecycle state, events, amounts, currency, refunds, and dispute evidence.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/stripe-payment-investigation && cp -r /tmp/stripe-payment-investigation/examples/plugin-packages/stripe/skills/stripe-payment-investigation ~/.claude/skills/stripe-payment-investigationSKILL.md
# Stripe Payment Investigation 1. Confirm test or live mode before retrieving or changing anything. 2. Resolve exact customer, PaymentIntent, Charge, Invoice, refund, or dispute IDs from trusted input. 3. Read the lifecycle and relevant events, keeping amount and currency attached to every conclusion. 4. Separate customer-visible outcome, Stripe state, integration behavior, and next action. 5. Do not issue a refund, retry, capture, cancel, or update an object during a diagnosis-only request. Redact unnecessary personal and payment data. Never infer live mode from an object description.
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.