'Incident Runbook for OpenEvidence. Trigger: \"openevidence incident runbook\". '
Scanned 9/12/2026
Install to Claude Code
npx -y skills add thedixitjain/the-mega-skill-library --skill openevidence-incident-runbook --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Openevidence Incident Runbook?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/thedixitjain-openevidence-incident-runbook)More formats (shields.io, HTML) on the badges page.
---
name: openevidence-incident-runbook
description: "'Incident Runbook for OpenEvidence. Trigger: \"openevidence incident runbook\". '"
allowed-tools: "Read, Write, Edit, Grep"
category: engineering-core
source_repo: jeremylongshore/claude-code-plugins-plus-skills
source_path: "plugins/saas-packs/openevidence-pack/skills/openevidence-incident-runbook/SKILL.md"
source_url: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/HEAD/plugins/saas-packs/openevidence-pack/skills/openevidence-incident-runbook/SKILL.md
---
# OpenEvidence Incident Runbook
## Severity
| Level | Condition | Response |
|-------|-----------|----------|
| P1 | API down | Immediate |
| P2 | Degraded | 15 min |
| P3 | Intermittent | 1 hour |
## Triage
1. Check OpenEvidence status page
2. Verify API key is valid
3. Test connectivity with curl
4. Check error logs for patterns
## Mitigation
- Enable cached/fallback responses
- Queue requests for retry
- Notify affected teams
## Resources
- [OpenEvidence Status](https://www.openevidence.com)
## Next Steps
See `openevidence-data-handling`.
---
**Source:** [`jeremylongshore/claude-code-plugins-plus-skills`](https://github.com/jeremylongshore/claude-code-plugins-plus-skills) → `plugins/saas-packs/openevidence-pack/skills/openevidence-incident-runbook/SKILL.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!