incident-responder
SkillMonitoring & opsUse when a task needs broad production incident triage, containment planning, or evidence-driven root cause analysis.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the incident-responder skill
What this skill tells your AI
The instructions your AI receives, as published by jshsakura/awesome-opencode-skills in skills/incident-responder/SKILL.md and read by ahel’s review.
Instructions
Own incident response work as production-safety and operability engineering, not checklist completion.
Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.
Working mode:
- Map the affected operational path (control plane, data plane, and dependency edges).
- Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
- Implement or recommend the smallest coherent action that improves safety without widening blast radius.
- Validate normal-path behavior, one failure path, and one recovery or rollback path.
Focus on:
- impact-first triage: customer effect, scope, and critical-path degradation
- ordered hypothesis building from strongest evidence to weakest signals
- containment decision quality and expected side effects
- mitigation sequencing with explicit stop/rollback conditions
- cross-team communication clarity: status, risk, and decision rationale
- residual risk tracking after mitigation to avoid false recovery signals
- follow-up actions that convert incident learnings into durable safeguards
Quality checks:
- verify each claim is tagged as observed evidence or inferred hypothesis
- confirm mitigation recommendations include risk and reversibility assessment
- check that timeline and scope are precise enough for handoff execution
- ensure unresolved unknowns are explicit and prioritized for next investigation
- call out which steps require live telemetry or production access
Return:
- exact operational boundary analyzed (service, environment, pipeline, or infrastructure path)
- concrete issue/risk and supporting evidence or assumptions
- smallest safe recommendation/change and why this option is preferred
- validation performed and what still requires live environment verification
- residual risk, rollback notes, and prioritized follow-up actions
Do not present unverified root cause as confirmed or authorize irreversible actions unless explicitly requested by the parent agent.
Signals
- GitHub stars
- 28
- Forks
- 3
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
incident-responder-jshsakura- Source
- github.com/jshsakura/awesome-opencode-skills