Payment Incident Responder — 技能 — openclaw中文资讯站

技能详情（站内镜像，无评论）

Coordinate payment incident response with structured triage, blast-radius assessment, mitigation actions, stakeholder communication, reconciliation recovery,...

媒体与内容

作者：ASP @anugotta

许可证：MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本：v1.0.0

统计：⭐ 0 · 27 · 0 current installs · 0 all-time installs

⭐ 0

安装量（当前） 0

🛡 VirusTotal ：良性 · OpenClaw ：良性

Package：anugotta/payment-incident-responder

安全扫描（ClawHub）

VirusTotal ：良性
OpenClaw ：良性

OpenClaw 评估

This skill is an instruction-only incident response playbook and the files, requirements, and instructions are consistent with that purpose.

目的

The name/description match the included playbooks, checklists, and templates. No binaries, credentials, or unusual system access are requested — appropriate for an operational guidance skill.

说明范围

SKILL.md and included files contain only guidance, templates, and references to the bundled files (setup/validation/playbook). There are no commands, hidden endpoints, or instructions to read unrelated files or exfiltrate data.

安装机制

No install spec or code files that would write or execute code on the host — lowest-risk instruction-only distribution.

证书

The skill requests no environment variables, credentials, or config paths, which is proportionate for a documentation/playbook skill.

持久

always is false and the skill does not request to modify agent/system configuration. Autonomous invocation is allowed by platform default but the skill's content is read-only guidance.

综合结论

This is a read-only incident response playbook and appears internally consistent, but before installing you should: verify the publisher/ownership (source is listed as unknown), review templates for compliance with your legal/finance policies, ensure the agent will not be given any permission to execute payments or automated remediation without human approval, test the playbook in drills, and confirm communication templates map to your approve…

安装（复制给龙虾 AI）

将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Payment Incident Responder」。简介：Coordinate payment incident response with structured triage, blast-radius asses…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/anugotta/payment-incident-responder/SKILL.md
（来源：yingzhi8.cn 技能库）

SKILL.md

打开原始 SKILL.md（GitHub raw）

---
name: payment-incident-responder
description: Coordinate payment incident response with structured triage, blast-radius assessment, mitigation actions, stakeholder communication, reconciliation recovery, and postmortem tracking.
metadata: {"openclaw":{"emoji":"🚨","homepage":"https://www.rbi.org.in/scripts/BS_ViewMasDirections.aspx?id=12898"}}
---

# Payment Incident Responder

## Purpose

Help teams respond to payment incidents quickly and consistently:

- detect and classify incident severity
- define immediate containment actions
- coordinate internal/external communication
- restore correctness via reconciliation and data repair
- produce postmortem action items

## Disclaimer

This skill provides operational guidance only. It does not execute payments, reverse transactions, or replace legal/compliance decisions.

Use at your own risk. The skill author/publisher/developer is not liable for direct or indirect losses, fraud, penalties, downtime, or damages arising from use or misuse of this guidance.

## Incident severity model

- `P0`: broad outage / incorrect success/failure state at scale
- `P1`: major degradation with partial workaround
- `P2`: limited impact to specific cohorts or features
- `P3`: minor issue, low customer impact

## Standard response workflow

1. **Acknowledge and assign roles**
   - incident commander
   - tech lead
   - comms owner
   - reconciliation owner

2. **Establish blast radius**
   - affected methods/regions/providers
   - impacted users/orders
   - error signatures and trend window

3. **Contain**
   - freeze risky deploys
   - enable degraded mode messaging
   - pause high-risk paths if needed

4. **Diagnose**
   - check webhook pipeline, API errors, queue lag, provider status
   - identify first failing component and triggering change

5. **Mitigate and recover**
   - apply safe rollback/fix
   - reconcile pending and mismatched states
   - verify customer-facing correctness

6. **Close and learn**
   - final incident summary
   - postmortem with owner/due-date action items

## Guardrails

- Never communicate "resolved" before metrics and correctness checks pass.
- Never run blind retries that can create duplicate charges.
- Always include transaction reference IDs in customer/support comms.
- Keep all decisions time-stamped in incident log.

## Output format

When invoked, return:

1. severity + current phase
2. top 3 immediate actions
3. customer impact summary
4. next update time and owner
5. reconciliation and correctness checklist

## Setup

Read [setup.md](setup.md) on first use.

## Validation

Run [validation-checklist.md](validation-checklist.md) for drills and live incidents.

## References

- Triage and mitigation templates: [incident-playbook.md](incident-playbook.md)
- Stakeholder/customer comms templates: [comms-templates.md](comms-templates.md)
- Post-incident tracking template: [postmortem-template.md](postmortem-template.md)
- Launch/readiness checks: [validation-checklist.md](validation-checklist.md)