Review and execute explicitly requested Stripe writes with exact environment, object, amount, currency, customer, and irreversible-effect confirmation.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add Devin-AXIS/iPolloWork --skill stripe-safe-operations --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Stripe Safe Operations?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/devin-axis-stripe-safe-operations)More formats (shields.io, HTML) on the badges page.
---
name: stripe-safe-operations
description: Review and execute explicitly requested Stripe writes with exact environment, object, amount, currency, customer, and irreversible-effect confirmation.
disable-model-invocation: false
---
# Stripe Safe Operations
Use this skill for refunds, cancellations, subscription changes, or other material Stripe writes.
1. Read the target object immediately before acting.
2. Present test/live mode, account, object ID, customer, amount and currency, current state, requested change, and irreversible effects.
3. Require explicit user confirmation for the exact operation. A general request to investigate is not confirmation to write.
4. Execute once and avoid blind retries when the result is uncertain.
5. Re-read the object and report the final state and identifiers.
Never expose credentials or full sensitive payment details. Never switch from test to live mode implicitly.
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', ...