openevidence-incident-runbook

Featured

Incident Runbook for OpenEvidence. Trigger: "openevidence incident runbook".

AI & Automation 2,359 stars 334 forks Updated today MIT

Install

View on GitHub

Quality Score: 97/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
28
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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`.

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
8 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Anthropic · AI

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

ir-runbook

Incident Response runbook — NIST SP 800-61 phases (Preparation/Detection-Analysis/Containment-Eradication-Recovery/Lessons-Learned), per-scenario playbooks (ransomware, BEC, data exfil, credential compromise, cloud), regulatory reporting (NIS2 24h/72h, AVG breach 72h, DORA), comms templates, and post-incident review.

4 Updated 2 weeks ago
roodlicht
AI & Automation Solid

runbook-gen

Generate operations runbooks and post-mortems for incident response — severity matrix, decision trees, escalation paths, war room setup (Slack/Zoom), status page updates, customer comms templates, and blameless post-mortems with action items.

96 Updated yesterday
EliasOulkadi
AI & Automation Featured

cohere-incident-runbook

Execute Cohere incident response procedures with triage, mitigation, and postmortem. Use when responding to Cohere API outages, investigating errors, or running post-incident reviews for Cohere integration failures. Trigger with phrases like "cohere incident", "cohere outage", "cohere down", "cohere on-call", "cohere emergency", "cohere broken".

2,359 Updated today
jeremylongshore