payment-incident-responder

What This Skill Does

The payment-incident-responder skill is a specialized operational framework designed to bring structure and reliability to high-stakes financial service disruptions. It serves as a tactical assistant for engineering and operations teams during payment-related incidents. By codifying the triage process, this skill ensures that teams move beyond reactive panic into a systematic containment and resolution loop. It tracks incident severity, mandates role assignment, enforces blast-radius assessment, and standardizes communication protocols. Crucially, it integrates a rigorous reconciliation checklist to ensure that data integrity is restored alongside system availability, preventing the common pitfalls of double charges or orphaned transaction states.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/anugotta/payment-incident-responder Ensure you have read the setup.md file provided in the repository to configure your environment variables and webhook connections before your first production use.

Use Cases

This skill is ideal for payment engineers, site reliability engineers (SREs), and incident commanders managing checkout failures, gateway outages, or asynchronous webhook delays. It is specifically designed for environments handling high-volume transaction processing where manual error-prone interventions could lead to financial losses. It acts as a force multiplier during a crisis, ensuring that no technical steps are skipped and that stakeholders remain informed with accurate, timestamped data.

Example Prompts

1. "I am declaring a P1 incident for the Stripe integration. Can you initiate the responder flow, assign roles, and help me map the blast radius based on the last 30 minutes of logs?"
2. "We have a batch of orders stuck in 'pending' status after the database deployment. Please generate a reconciliation checklist and help me identify which transactions require manual verification versus automated repair."
3. "The current incident is mitigated. Please draft a final incident summary for leadership and provide the template for the post-mortem action item tracking."

Tips & Limitations

This skill is designed as an operational guide and is not a substitute for financial logic. Never allow the agent to execute autonomous reversals or bulk refunds without explicit human verification of the transaction IDs. Always prioritize the 'Guardrails' section of the documentation—specifically the rule against blind retries, which can cause severe customer impact through duplicate billing. Treat the output as professional guidance that requires technical human review at every stage to ensure regulatory compliance and data correctness.