Incident Response
Production incident and major-error response workflow. Use for outages, degraded service, repeated hook/tool failures, security incidents, data loss, rollback decisions, on-call triage, or when MAJOR_ERRORS.md shows blocking failures.
Install
$ agentstack add skill-jh941213-codex-lattice-incident-response ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jh941213-codex-lattice-incident-response) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Incident Response
Use this skill when a production incident, major repeated error, rollback decision, or on-call triage is involved.
Workflow
- Stabilize first: stop risky changes, preserve logs, and identify the affected service or workflow.
- Classify severity in
docs/harness/INCIDENT_RESPONSE.md. - Capture timeline, impact, suspected trigger, current mitigation, and owner.
- Prefer read-only diagnostics before mutating systems.
- If rollback is safer than forward fix, document the rollback command and validation.
- Update model-visible major errors only with information the next agent must read.
- After mitigation, create or update
docs/harness/POSTMORTEM_TEMPLATE.md.
Severity Guide
SEV0: data loss, security exposure, total outage, destructive automation.SEV1: customer-visible outage or broken critical workflow.SEV2: partial degradation, failed deployment, repeated operational failure.SEV3: non-urgent defect, flaky check, noisy alert.
Required Output
Return:
- severity
- impact
- immediate mitigation
- diagnostics run
- rollback or forward-fix decision
- follow-up action items
- postmortem required: yes/no
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jh941213
- Source: jh941213/codex-lattice
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.