openevidence-incident-runbook
Standardized procedure for triaging and mitigating errors in OpenEvidence integrations.
Install
mkdir -p .claude/skills/openevidence-incident-runbook && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8067" && unzip -o skill.zip -d .claude/skills/openevidence-incident-runbook && rm skill.zipInstalls to .claude/skills/openevidence-incident-runbook
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Incident Runbook for OpenEvidence.Key capabilities
- →Categorize incident severity based on API availability
- →Verify OpenEvidence API key validity
- →Test network connectivity using curl
- →Analyze error logs for failure patterns
- →Implement fallback response mechanisms
- →Queue failed requests for subsequent retry
How it works
The skill follows a defined severity matrix to categorize incidents and provides a checklist for triage, including status page verification and connectivity testing. Mitigation involves switching to cached responses and queuing requests for retry.
Inputs & outputs
When to use openevidence-incident-runbook
- →Triage API outages
- →Mitigate degraded service conditions
- →Conduct post-incident reviews
- →Verify system connectivity
About this skill
OpenEvidence Incident Runbook
Severity
| Level | Condition | Response |
|---|---|---|
| P1 | API down | Immediate |
| P2 | Degraded | 15 min |
| P3 | Intermittent | 1 hour |
Triage
- Check OpenEvidence status page
- Verify API key is valid
- Test connectivity with curl
- Check error logs for patterns
Mitigation
- Enable cached/fallback responses
- Queue requests for retry
- Notify affected teams
Resources
Next Steps
See openevidence-data-handling.
Prerequisites
How it compares
This skill provides a standardized incident response protocol specifically for OpenEvidence rather than relying on manual troubleshooting steps.
Compared to similar skills
openevidence-incident-runbook side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| openevidence-incident-runbook (this skill) | 0 | 27d | Review | Intermediate |
| firecrawl-incident-runbook | 1 | 27d | Review | Intermediate |
| perplexity-incident-runbook | 0 | 27d | Review | Intermediate |
| managing-filestack | 0 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
firecrawl-incident-runbook
jeremylongshore
Execute FireCrawl incident response procedures with triage, mitigation, and postmortem. Use when responding to FireCrawl-related outages, investigating errors, or running post-incident reviews for FireCrawl integration failures. Trigger with phrases like "firecrawl incident", "firecrawl outage", "firecrawl down", "firecrawl on-call", "firecrawl emergency", "firecrawl broken".
perplexity-incident-runbook
jeremylongshore
Execute Perplexity incident response procedures with triage, mitigation, and postmortem. Use when responding to Perplexity-related outages, investigating errors, or running post-incident reviews for Perplexity integration failures. Trigger with phrases like "perplexity incident", "perplexity outage", "perplexity down", "perplexity on-call", "perplexity emergency", "perplexity broken".
managing-filestack
cloudthinker-ai
|
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
n8n-workflow-patterns
czlonkowski
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.