incident-report
Write clear, factual incident reports that document what happened, impact, response, root causes, and follow-up actions. Use after operational, security, safety, or customer-impacting incidents when a formal written record is required.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- incident-report
- description
- Write clear, factual incident reports that document what happened, impact, response, root causes, and follow-up actions. Use after operational, security, safety, or customer-impacting incidents when a formal written record is required.
03 SKILL.md 正文
Incident Report
Overview
Incident reports create a reliable record for learning and accountability. They focus on facts, timeline, impact, and improvement — not blame.
When to Use
- Production or operational incidents
- Security incidents
- Safety or compliance incidents
- Significant customer-impacting events
Recommended Structure
- Summary (what, when, impact)
- Timeline of key events
- Impact assessment
- Detection and response actions
- Root cause analysis
- Contributing factors
- Corrective and preventive actions
- Lessons learned
- Appendix (logs, graphs, evidence)
Principles
- Stick to verifiable facts in the timeline
- Quantify impact where possible
- Separate immediate fixes from longer-term improvements
- Assign owners and due dates to action items
- Write so someone uninvolved can understand the event
Verification
- [ ] Timeline is clear and factual
- [ ] Impact is described concretely
- [ ] Actions have owners
- [ ] Root cause analysis goes beyond the surface symptom
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.