[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F8CHQDD2PH4T5360N14EY3":3,"skill-same:01M6F8CHQDD2PH4T5360N14EY3":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6F8CHQDD2PH4T5360N14EY3","openevidence-incident-runbook",null,"Execute OpenEvidence incident response procedures with triage, mitigation, and postmortem.\nUse when responding to OpenEvidence-related outages, investigating errors,\nor running post-incident reviews for clinical AI integration failures.\nTrigger with phrases like \"openevidence incident\", \"openevidence outage\",\n\"openevidence down\", \"openevidence emergency\", \"clinical ai broken\".","Dicklesworthstone\u002Fpi_agent_rust","Dicklesworthstone","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35050222?v=4","01M6CG26AR942CSVMN1M5E3DSE","Jeff Emanuel","01M6CG26EPP71PSHW1VDS71121",1992,"MIT","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fopenevidence-pack\u002Fskills\u002Fopenevidence-incident-runbook\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"runbook","openevidence incident runbook","incident","clinical","running","when","down","for","errors","reviews","with","post","trigger","io","incident response","use","read","broken","curl","grep","postmortem","Bash","kubectl","integration","2026-11-10 10:12:30",false,"---\nname: openevidence-incident-runbook\ndescription: |\n  Execute OpenEvidence incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to OpenEvidence-related outages, investigating errors,\n  or running post-incident reviews for clinical AI integration failures.\n  Trigger with phrases like \"openevidence incident\", \"openevidence outage\",\n  \"openevidence down\", \"openevidence emergency\", \"clinical ai broken\".\nallowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# OpenEvidence Incident Runbook\n\n## Overview\nRapid incident response procedures for OpenEvidence clinical AI integration outages in healthcare environments.\n\n## Prerequisites\n- Access to OpenEvidence status page\n- kubectl access to production cluster\n- Prometheus\u002FGrafana access\n- PagerDuty or on-call system access\n- Communication channels (Slack, Teams)\n\n## Severity Levels\n\n| Level | Definition | Response Time | Impact | Examples |\n|-------|------------|---------------|--------|----------|\n| P1 | Complete outage | \u003C 15 min | Patient care affected | API unreachable, all queries failing |\n| P2 | Degraded service | \u003C 1 hour | Clinical workflows slowed | High latency, partial failures |\n| P3 | Minor impact | \u003C 4 hours | Non-critical features | DeepConsult delays, webhook issues |\n| P4 | No user impact | Next business day | Monitoring gaps | Alert noise, logging issues |\n\n## Critical Note: Clinical Impact\n\n**OpenEvidence outages may affect clinical decision-making. Always:**\n1. Communicate clearly with clinical staff about degraded service\n2. Ensure fallback procedures are known (manual guidelines lookup)\n3. Never claim the system is available if it's degraded\n4. Document any clinical impact for post-incident review\n\n## Quick Triage\n\n### Step 1: Initial Assessment (2 minutes)\n```bash\n# 1. Check OpenEvidence status\ncurl -sf https:\u002F\u002Fstatus.openevidence.com\u002Fapi\u002Fv2\u002Fsummary.json | jq '.status'\n\n# 2. Check our integration health\ncurl -sf https:\u002F\u002Fapi.yourhealthcare.com\u002Fhealth\u002Fopenevidence | jq\n\n# 3. Check error rate (last 5 min)\ncurl -s 'localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(openevidence_errors_total[5m])' | jq '.data.result[0].value[1]'\n\n# 4. Recent error logs\nkubectl logs -l app=clinical-evidence-api --since=5m | grep -i error | tail -20\n```\n\n### Step 2: Decision Tree\n```\nOpenEvidence API returning errors?\n├─ YES: Is status.openevidence.com showing incident?\n│   ├─ YES → OpenEvidence outage. Enable fallback. Wait for resolution.\n│   └─ NO → Our integration issue. Check credentials, config, network.\n└─ NO: Is our service healthy?\n    ├─ YES → Likely resolved or intermittent. Monitor closely.\n    └─ NO → Our infrastructure issue. Check pods, memory, network.\n```\n\n## Incident Response by Error Type\n\n### 401\u002F403 - Authentication Errors\n```bash\n# Verify API key is set\nkubectl get secret openevidence-secrets -o jsonpath='{.data.api-key}' | base64 -d | wc -c\n\n# Check if key format is correct (should start with oe_)\nkubectl get secret openevidence-secrets -o jsonpath='{.data.api-key}' | base64 -d | head -c 3\n\n# REMEDIATION: Rotate API key\n# 1. Generate new key in OpenEvidence dashboard\n# 2. Update secret\nkubectl create secret generic openevidence-secrets \\\n  --from-literal=api-key=NEW_KEY \\\n  --from-literal=org-id=EXISTING_ORG_ID \\\n  --dry-run=client -o yaml | kubectl apply -f -\n\n# 3. Restart pods to pick up new secret\nkubectl rollout restart deployment\u002Fclinical-evidence-api\n```\n\n### 429 - Rate Limited\n```bash\n# Check current rate limit status\ncurl -s -H \"Authorization: Bearer ${OPENEVIDENCE_API_KEY}\" \\\n  https:\u002F\u002Fapi.openevidence.com\u002Fv1\u002Frate-limit | jq\n\n# Check rate limit metrics\ncurl -s 'localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=openevidence_rate_limit_remaining' | jq\n\n# REMEDIATION: Enable request queuing\nkubectl set env deployment\u002Fclinical-evidence-api RATE_LIMIT_MODE=queue\n\n# Long-term: Contact OpenEvidence for limit increase\n# Enterprise: sales@openevidence.com\n```\n\n### 500\u002F503 - OpenEvidence Server Errors\n```bash\n# Confirm it's OpenEvidence-side\ncurl -v -H \"Authorization: Bearer ${OPENEVIDENCE_API_KEY}\" \\\n  https:\u002F\u002Fapi.openevidence.com\u002Fhealth 2>&1 | grep \"\u003C HTTP\"\n\n# REMEDIATION: Enable graceful degradation\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=true\n\n# Notify clinical staff\n.\u002Fscripts\u002Fnotify-clinical-degraded.sh\n\n# Update status page\n.\u002Fscripts\u002Fupdate-status-page.sh degraded \"OpenEvidence service degraded\"\n```\n\n### Timeout Errors\n```bash\n# Check current timeout setting\nkubectl get deployment clinical-evidence-api -o jsonpath='{.spec.template.spec.containers[0].env}' | jq '.[] | select(.name==\"OPENEVIDENCE_TIMEOUT\")'\n\n# Check network latency to OpenEvidence\ntime curl -sf https:\u002F\u002Fapi.openevidence.com\u002Fhealth\n\n# REMEDIATION: Increase timeout temporarily\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_TIMEOUT=60000\n\n# Check for network issues\nkubectl exec -it deployment\u002Fclinical-evidence-api -- nslookup api.openevidence.com\nkubectl exec -it deployment\u002Fclinical-evidence-api -- traceroute api.openevidence.com\n```\n\n## Fallback Procedures\n\n### Enable Graceful Degradation\n```typescript\n\u002F\u002F When OpenEvidence is unavailable, return helpful fallback\nconst FALLBACK_RESPONSE = {\n  answer: 'Clinical evidence service is temporarily unavailable. ' +\n          'Please consult UpToDate, DynaMed, or current clinical guidelines directly.',\n  citations: [],\n  confidence: 0,\n  fallback: true,\n  disclaimer: 'This is a fallback response. The AI clinical decision support is currently unavailable.',\n};\n\nasync function clinicalQueryWithFallback(question: string) {\n  try {\n    return await openEvidence.query(question);\n  } catch (error) {\n    \u002F\u002F Log for incident tracking\n    logger.error({ error, question: '[REDACTED]' }, 'OpenEvidence query failed, using fallback');\n\n    \u002F\u002F Alert operations\n    await alertOps('OpenEvidence unavailable, fallback active');\n\n    return FALLBACK_RESPONSE;\n  }\n}\n```\n\n### Notify Clinical Staff\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fnotify-clinical-degraded.sh\n\nMESSAGE=\"[Clinical Alert] AI clinical decision support (OpenEvidence) is experiencing issues.\nPlease use alternative resources (UpToDate, DynaMed, clinical guidelines) until further notice.\nStatus updates: https:\u002F\u002Fstatus.yourhealthcare.com\"\n\n# Send to clinical Slack channel\ncurl -X POST -H 'Content-type: application\u002Fjson' \\\n  --data \"{\\\"text\\\":\\\"$MESSAGE\\\"}\" \\\n  \"$CLINICAL_SLACK_WEBHOOK\"\n\n# Send email to clinical leadership\n.\u002Fscripts\u002Fsend-clinical-email.sh \"$MESSAGE\"\n```\n\n## Communication Templates\n\n### Internal (Slack\u002FTeams)\n```markdown\n:red_circle: **P1 INCIDENT: OpenEvidence Clinical AI**\n**Status:** INVESTIGATING\n**Started:** [timestamp]\n**Impact:** Clinical queries returning errors\u002Fdegraded\n**Current Action:** [What you're doing]\n**Fallback:** Graceful degradation enabled\n**Next Update:** [time]\n**Incident Commander:** @[name]\n```\n\n### External (Clinical Staff)\n```markdown\n**Clinical Decision Support Alert**\n\nOur AI-powered clinical evidence tool (OpenEvidence) is currently experiencing issues.\n\n**Impact:** Clinical queries may be slower or unavailable\n**Alternative Resources:**\n- UpToDate: uptodate.com\n- DynaMed: dynamed.com\n- Clinical guidelines directly\n\nWe are actively working to restore service and will provide updates.\n\nLast Updated: [timestamp]\n```\n\n### Status Page\n```markdown\n**OpenEvidence Integration Issue**\n\nWe're experiencing issues with our clinical AI integration.\nSome clinical evidence queries may be slow or unavailable.\n\n**Impact:** [Specific impact]\n**Workaround:** Use alternative clinical resources\n\nWe're actively investigating and will provide updates.\n\nLast Updated: [timestamp]\n```\n\n## Post-Incident Procedures\n\n### Evidence Collection\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fcollect-incident-evidence.sh\n\nINCIDENT_ID=${1:-$(date +%Y%m%d-%H%M)}\nOUTPUT_DIR=\"incidents\u002F${INCIDENT_ID}\"\nmkdir -p \"$OUTPUT_DIR\"\n\n# Export logs (last 2 hours)\nkubectl logs -l app=clinical-evidence-api --since=2h > \"$OUTPUT_DIR\u002Fapp-logs.txt\"\n\n# Export metrics\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=openevidence_errors_total&start=$(date -d '2 hours ago' +%s)&end=$(date +%s)&step=60\" > \"$OUTPUT_DIR\u002Ferror-metrics.json\"\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=openevidence_request_duration_seconds&start=$(date -d '2 hours ago' +%s)&end=$(date +%s)&step=60\" > \"$OUTPUT_DIR\u002Flatency-metrics.json\"\n\n# Export alerts\ncurl \"localhost:9093\u002Fapi\u002Fv2\u002Falerts\" > \"$OUTPUT_DIR\u002Falerts.json\"\n\n# Sanitize (remove any PHI)\n.\u002Fscripts\u002Fsanitize-incident-data.sh \"$OUTPUT_DIR\"\n\necho \"Evidence collected in $OUTPUT_DIR\"\n```\n\n### Postmortem Template\n```markdown\n## Incident Postmortem: OpenEvidence [Error Type]\n\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n**Incident Commander:** [Name]\n\n### Summary\n[1-2 sentence description of what happened]\n\n### Clinical Impact\n- Queries affected: [number]\n- Users impacted: [number]\n- Fallback used: Yes\u002FNo\n- Any patient care impact: [description or \"None identified\"]\n\n### Timeline (UTC)\n| Time | Event |\n|------|-------|\n| HH:MM | First alert fired |\n| HH:MM | Incident declared |\n| HH:MM | Fallback enabled |\n| HH:MM | Root cause identified |\n| HH:MM | Fix deployed |\n| HH:MM | Service restored |\n| HH:MM | Incident closed |\n\n### Root Cause\n[Technical explanation of what caused the incident]\n\n### Contributing Factors\n- [Factor 1]\n- [Factor 2]\n\n### What Went Well\n- [Positive outcome 1]\n- [Positive outcome 2]\n\n### What Could Be Improved\n- [Improvement area 1]\n- [Improvement area 2]\n\n### Action Items\n| Action | Owner | Due Date | Status |\n|--------|-------|----------|--------|\n| [Preventive measure] | [Name] | [Date] | Pending |\n| [Detection improvement] | [Name] | [Date] | Pending |\n\n### Lessons Learned\n[Key takeaways for the team]\n```\n\n## Quick Reference Commands\n\n```bash\n# One-line health check\ncurl -sf https:\u002F\u002Fapi.yourhealthcare.com\u002Fhealth\u002Fopenevidence | jq '.status' || echo \"UNHEALTHY\"\n\n# Check OpenEvidence status\ncurl -sf https:\u002F\u002Fstatus.openevidence.com\u002Fapi\u002Fv2\u002Fsummary.json | jq '.status.indicator'\n\n# Error rate last 5 min\ncurl -s 'localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(openevidence_errors_total[5m])\u002Frate(openevidence_requests_total[5m])*100' | jq '.data.result[0].value[1]'\n\n# Enable fallback mode\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=true\n\n# Disable fallback mode (restore normal operation)\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=false\n\n# Restart pods\nkubectl rollout restart deployment\u002Fclinical-evidence-api\n\n# Watch pod status\nkubectl get pods -l app=clinical-evidence-api -w\n```\n\n## Output\n- Quick triage procedure completed\n- Issue identified and categorized\n- Remediation applied\n- Clinical staff notified\n- Evidence collected for postmortem\n\n## Resources\n- [OpenEvidence Status](https:\u002F\u002Fstatus.openevidence.com\u002F)\n- [OpenEvidence Support](mailto:support@openevidence.com)\n- Internal: [On-Call Runbook](internal-link)\n- Internal: [Escalation Matrix](internal-link)\n\n## Next Steps\nFor PHI data handling, see `openevidence-data-handling`.\n","# OpenEvidence Incident Runbook\n\n## Overview\nRapid incident response procedures for OpenEvidence clinical AI integration outages in healthcare environments.\n\n## Prerequisites\n- Access to OpenEvidence status page\n- kubectl access to production cluster\n- Prometheus\u002FGrafana access\n- PagerDuty or on-call system access\n- Communication channels (Slack, Teams)\n\n## Severity Levels\n\n| Level | Definition | Response Time | Impact | Examples |\n|-------|------------|---------------|--------|----------|\n| P1 | Complete outage | \u003C 15 min | Patient care affected | API unreachable, all queries failing |\n| P2 | Degraded service | \u003C 1 hour | Clinical workflows slowed | High latency, partial failures |\n| P3 | Minor impact | \u003C 4 hours | Non-critical features | DeepConsult delays, webhook issues |\n| P4 | No user impact | Next business day | Monitoring gaps | Alert noise, logging issues |\n\n## Critical Note: Clinical Impact\n\n**OpenEvidence outages may affect clinical decision-making. Always:**\n1. Communicate clearly with clinical staff about degraded service\n2. Ensure fallback procedures are known (manual guidelines lookup)\n3. Never claim the system is available if it's degraded\n4. Document any clinical impact for post-incident review\n\n## Quick Triage\n\n### Step 1: Initial Assessment (2 minutes)\n```bash\n# 1. Check OpenEvidence status\ncurl -sf https:\u002F\u002Fstatus.openevidence.com\u002Fapi\u002Fv2\u002Fsummary.json | jq '.status'\n\n# 2. Check our integration health\ncurl -sf https:\u002F\u002Fapi.yourhealthcare.com\u002Fhealth\u002Fopenevidence | jq\n\n# 3. Check error rate (last 5 min)\ncurl -s 'localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(openevidence_errors_total[5m])' | jq '.data.result[0].value[1]'\n\n# 4. Recent error logs\nkubectl logs -l app=clinical-evidence-api --since=5m | grep -i error | tail -20\n```\n\n### Step 2: Decision Tree\n```\nOpenEvidence API returning errors?\n├─ YES: Is status.openevidence.com showing incident?\n│   ├─ YES → OpenEvidence outage. Enable fallback. Wait for resolution.\n│   └─ NO → Our integration issue. Check credentials, config, network.\n└─ NO: Is our service healthy?\n    ├─ YES → Likely resolved or intermittent. Monitor closely.\n    └─ NO → Our infrastructure issue. Check pods, memory, network.\n```\n\n## Incident Response by Error Type\n\n### 401\u002F403 - Authentication Errors\n```bash\n# Verify API key is set\nkubectl get secret openevidence-secrets -o jsonpath='{.data.api-key}' | base64 -d | wc -c\n\n# Check if key format is correct (should start with oe_)\nkubectl get secret openevidence-secrets -o jsonpath='{.data.api-key}' | base64 -d | head -c 3\n\n# REMEDIATION: Rotate API key\n# 1. Generate new key in OpenEvidence dashboard\n# 2. Update secret\nkubectl create secret generic openevidence-secrets \\\n  --from-literal=api-key=NEW_KEY \\\n  --from-literal=org-id=EXISTING_ORG_ID \\\n  --dry-run=client -o yaml | kubectl apply -f -\n\n# 3. Restart pods to pick up new secret\nkubectl rollout restart deployment\u002Fclinical-evidence-api\n```\n\n### 429 - Rate Limited\n```bash\n# Check current rate limit status\ncurl -s -H \"Authorization: Bearer ${OPENEVIDENCE_API_KEY}\" \\\n  https:\u002F\u002Fapi.openevidence.com\u002Fv1\u002Frate-limit | jq\n\n# Check rate limit metrics\ncurl -s 'localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=openevidence_rate_limit_remaining' | jq\n\n# REMEDIATION: Enable request queuing\nkubectl set env deployment\u002Fclinical-evidence-api RATE_LIMIT_MODE=queue\n\n# Long-term: Contact OpenEvidence for limit increase\n# Enterprise: sales@openevidence.com\n```\n\n### 500\u002F503 - OpenEvidence Server Errors\n```bash\n# Confirm it's OpenEvidence-side\ncurl -v -H \"Authorization: Bearer ${OPENEVIDENCE_API_KEY}\" \\\n  https:\u002F\u002Fapi.openevidence.com\u002Fhealth 2>&1 | grep \"\u003C HTTP\"\n\n# REMEDIATION: Enable graceful degradation\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=true\n\n# Notify clinical staff\n.\u002Fscripts\u002Fnotify-clinical-degraded.sh\n\n# Update status page\n.\u002Fscripts\u002Fupdate-status-page.sh degraded \"OpenEvidence service degraded\"\n```\n\n### Timeout Errors\n```bash\n# Check current timeout setting\nkubectl get deployment clinical-evidence-api -o jsonpath='{.spec.template.spec.containers[0].env}' | jq '.[] | select(.name==\"OPENEVIDENCE_TIMEOUT\")'\n\n# Check network latency to OpenEvidence\ntime curl -sf https:\u002F\u002Fapi.openevidence.com\u002Fhealth\n\n# REMEDIATION: Increase timeout temporarily\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_TIMEOUT=60000\n\n# Check for network issues\nkubectl exec -it deployment\u002Fclinical-evidence-api -- nslookup api.openevidence.com\nkubectl exec -it deployment\u002Fclinical-evidence-api -- traceroute api.openevidence.com\n```\n\n## Fallback Procedures\n\n### Enable Graceful Degradation\n```typescript\n\u002F\u002F When OpenEvidence is unavailable, return helpful fallback\nconst FALLBACK_RESPONSE = {\n  answer: 'Clinical evidence service is temporarily unavailable. ' +\n          'Please consult UpToDate, DynaMed, or current clinical guidelines directly.',\n  citations: [],\n  confidence: 0,\n  fallback: true,\n  disclaimer: 'This is a fallback response. The AI clinical decision support is currently unavailable.',\n};\n\nasync function clinicalQueryWithFallback(question: string) {\n  try {\n    return await openEvidence.query(question);\n  } catch (error) {\n    \u002F\u002F Log for incident tracking\n    logger.error({ error, question: '[REDACTED]' }, 'OpenEvidence query failed, using fallback');\n\n    \u002F\u002F Alert operations\n    await alertOps('OpenEvidence unavailable, fallback active');\n\n    return FALLBACK_RESPONSE;\n  }\n}\n```\n\n### Notify Clinical Staff\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fnotify-clinical-degraded.sh\n\nMESSAGE=\"[Clinical Alert] AI clinical decision support (OpenEvidence) is experiencing issues.\nPlease use alternative resources (UpToDate, DynaMed, clinical guidelines) until further notice.\nStatus updates: https:\u002F\u002Fstatus.yourhealthcare.com\"\n\n# Send to clinical Slack channel\ncurl -X POST -H 'Content-type: application\u002Fjson' \\\n  --data \"{\\\"text\\\":\\\"$MESSAGE\\\"}\" \\\n  \"$CLINICAL_SLACK_WEBHOOK\"\n\n# Send email to clinical leadership\n.\u002Fscripts\u002Fsend-clinical-email.sh \"$MESSAGE\"\n```\n\n## Communication Templates\n\n### Internal (Slack\u002FTeams)\n```markdown\n:red_circle: **P1 INCIDENT: OpenEvidence Clinical AI**\n**Status:** INVESTIGATING\n**Started:** [timestamp]\n**Impact:** Clinical queries returning errors\u002Fdegraded\n**Current Action:** [What you're doing]\n**Fallback:** Graceful degradation enabled\n**Next Update:** [time]\n**Incident Commander:** @[name]\n```\n\n### External (Clinical Staff)\n```markdown\n**Clinical Decision Support Alert**\n\nOur AI-powered clinical evidence tool (OpenEvidence) is currently experiencing issues.\n\n**Impact:** Clinical queries may be slower or unavailable\n**Alternative Resources:**\n- UpToDate: uptodate.com\n- DynaMed: dynamed.com\n- Clinical guidelines directly\n\nWe are actively working to restore service and will provide updates.\n\nLast Updated: [timestamp]\n```\n\n### Status Page\n```markdown\n**OpenEvidence Integration Issue**\n\nWe're experiencing issues with our clinical AI integration.\nSome clinical evidence queries may be slow or unavailable.\n\n**Impact:** [Specific impact]\n**Workaround:** Use alternative clinical resources\n\nWe're actively investigating and will provide updates.\n\nLast Updated: [timestamp]\n```\n\n## Post-Incident Procedures\n\n### Evidence Collection\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fcollect-incident-evidence.sh\n\nINCIDENT_ID=${1:-$(date +%Y%m%d-%H%M)}\nOUTPUT_DIR=\"incidents\u002F${INCIDENT_ID}\"\nmkdir -p \"$OUTPUT_DIR\"\n\n# Export logs (last 2 hours)\nkubectl logs -l app=clinical-evidence-api --since=2h > \"$OUTPUT_DIR\u002Fapp-logs.txt\"\n\n# Export metrics\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=openevidence_errors_total&start=$(date -d '2 hours ago' +%s)&end=$(date +%s)&step=60\" > \"$OUTPUT_DIR\u002Ferror-metrics.json\"\ncurl \"localhost:9090\u002Fapi\u002Fv1\u002Fquery_range?query=openevidence_request_duration_seconds&start=$(date -d '2 hours ago' +%s)&end=$(date +%s)&step=60\" > \"$OUTPUT_DIR\u002Flatency-metrics.json\"\n\n# Export alerts\ncurl \"localhost:9093\u002Fapi\u002Fv2\u002Falerts\" > \"$OUTPUT_DIR\u002Falerts.json\"\n\n# Sanitize (remove any PHI)\n.\u002Fscripts\u002Fsanitize-incident-data.sh \"$OUTPUT_DIR\"\n\necho \"Evidence collected in $OUTPUT_DIR\"\n```\n\n### Postmortem Template\n```markdown\n## Incident Postmortem: OpenEvidence [Error Type]\n\n**Date:** YYYY-MM-DD\n**Duration:** X hours Y minutes\n**Severity:** P[1-4]\n**Incident Commander:** [Name]\n\n### Summary\n[1-2 sentence description of what happened]\n\n### Clinical Impact\n- Queries affected: [number]\n- Users impacted: [number]\n- Fallback used: Yes\u002FNo\n- Any patient care impact: [description or \"None identified\"]\n\n### Timeline (UTC)\n| Time | Event |\n|------|-------|\n| HH:MM | First alert fired |\n| HH:MM | Incident declared |\n| HH:MM | Fallback enabled |\n| HH:MM | Root cause identified |\n| HH:MM | Fix deployed |\n| HH:MM | Service restored |\n| HH:MM | Incident closed |\n\n### Root Cause\n[Technical explanation of what caused the incident]\n\n### Contributing Factors\n- [Factor 1]\n- [Factor 2]\n\n### What Went Well\n- [Positive outcome 1]\n- [Positive outcome 2]\n\n### What Could Be Improved\n- [Improvement area 1]\n- [Improvement area 2]\n\n### Action Items\n| Action | Owner | Due Date | Status |\n|--------|-------|----------|--------|\n| [Preventive measure] | [Name] | [Date] | Pending |\n| [Detection improvement] | [Name] | [Date] | Pending |\n\n### Lessons Learned\n[Key takeaways for the team]\n```\n\n## Quick Reference Commands\n\n```bash\n# One-line health check\ncurl -sf https:\u002F\u002Fapi.yourhealthcare.com\u002Fhealth\u002Fopenevidence | jq '.status' || echo \"UNHEALTHY\"\n\n# Check OpenEvidence status\ncurl -sf https:\u002F\u002Fstatus.openevidence.com\u002Fapi\u002Fv2\u002Fsummary.json | jq '.status.indicator'\n\n# Error rate last 5 min\ncurl -s 'localhost:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(openevidence_errors_total[5m])\u002Frate(openevidence_requests_total[5m])*100' | jq '.data.result[0].value[1]'\n\n# Enable fallback mode\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=true\n\n# Disable fallback mode (restore normal operation)\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=false\n\n# Restart pods\nkubectl rollout restart deployment\u002Fclinical-evidence-api\n\n# Watch pod status\nkubectl get pods -l app=clinical-evidence-api -w\n```\n\n## Output\n- Quick triage procedure completed\n- Issue identified and categorized\n- Remediation applied\n- Clinical staff notified\n- Evidence collected for postmortem\n\n## Resources\n- [OpenEvidence Status](https:\u002F\u002Fstatus.openevidence.com\u002F)\n- [OpenEvidence Support](mailto:support@openevidence.com)\n- Internal: [On-Call Runbook](internal-link)\n- Internal: [Escalation Matrix](internal-link)\n\n## Next Steps\nFor PHI data handling, see `openevidence-data-handling`.\n",{"name":5,"author":48,"license":15,"version":49,"description":50,"allowed-tools":51},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute OpenEvidence incident response procedures with triage, mitigation, and postmortem.\nUse when responding to OpenEvidence-related outages, investigating errors,\nor running post-incident reviews for clinical AI integration failures.\nTrigger with phrases like \"openevidence incident\", \"openevidence outage\",\n\"openevidence down\", \"openevidence emergency\", \"clinical ai broken\".\n","Read, Grep, Bash(kubectl:*), Bash(curl:*)","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fopenevidence-pack\u002Fskills\u002Fopenevidence-incident-runbook",233,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust","https:\u002F\u002Fgithub.com\u002FDicklesworthstone","https:\u002F\u002Fwww.jeffreyemanuel.com\u002F","Building in NY","2026-11-15 01:54:15",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill openevidence-incident-runbook",{"tool":67,"command":68},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill openevidence-incident-runbook",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill openevidence-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fopenevidence-pack\u002Fskills\u002Fopenevidence-incident-runbook\u002FSKILL.md",true,[],[76,109,143,166,192,219],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":108},"01M6FCR7G5A005P364Z6ZWCJDP","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Ftheme-factory\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,29,106,107],"theme factory","factory","theme","docs","toolkit","generate","artifacts","SET","fly","slides","landing","html","styling","artifact","pages","themes","you","fonts","2026-11-11 15:11:14",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":43},"01M6FEGPPK0ZTKCCM0R3E3KS33","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000009","前端开发",[120,121,96,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,34,101,137,138,139,140,26,141,142],"web artifacts builder","web","artifacts builder","builder","frontend","css","components","react","component","routing","state management","state","shadcn","file","ui","Tools","Tailwind","single-file","simple","ui components","multi","jsx","suite",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":154,"publishedAt":43},"01M6FEE9VTK1W4GY21AKREJXRG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[150,153],{"categoryNo":151,"categoryName":152,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":117,"categoryName":118,"taxonomyType":87,"taxonomyTypeDesc":88},[155,156,157,124,158,159,121,160,94,161,134,162,163,164,165,29,26],"testing","webapp testing","webapp","screenshots","playwright","debugging","browser","logs","applications","behavior","local",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":43},"01M6FE20F7ZTQBFWKF4MPJ2SBX","neuropixels-analysis","Neuropixels neural recording analysis. Load SpikeGLX\u002FOpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen\u002FIBL curation, AI-assisted visual analysis, for Neuropixels 1.0\u002F2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,34,182,183,184,185,186,187,188,29,189,190,191,26,24],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","load",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":202,"publishedAt":43},"01M6FDP0PDK6F1GGX395C7625Z","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FSKILL.md",[199],{"categoryNo":200,"categoryName":201,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",[203,204,205,206,207,208,209,210,211,212,213,214,215,216,29,26,217,24,218],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","users","Existing","new",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":227,"publishedAt":43},"01M6FDM8Y7VK7NYG9SM7QPA3PW","notebooklm","Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FSKILL.md",[226],{"categoryNo":200,"categoryName":201,"taxonomyType":87,"taxonomyTypeDesc":88},[221,228,229,230,231,232,233,161,234,235,34,236,237,238,239,26,240],"google","browser automation","gemini","automation","auth","code","library","management","only","document","query","Citation","source"]