[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754T55Q7A74RS4WY81J1C0F":3,"skill-same:01M754T55Q7A74RS4WY81J1C0F":55},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M754T55Q7A74RS4WY81J1C0F","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\".","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fopenevidence-incident-runbook\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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>\ncompatible-with: claude-code, codex, openclaw\n---\n# OpenEvidence Incident Runbook\n\n## Table of Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nRapid incident response procedures for OpenEvidence clinical AI integration outages in healthcare environments. Includes severity classification, triage steps, error-specific remediation, fallback procedures, and postmortem templates.\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\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | API unreachable, all queries failing |\n| P2 | Degraded service | \u003C 1 hour | High latency, partial failures |\n| P3 | Minor impact | \u003C 4 hours | DeepConsult delays, webhook issues |\n| P4 | No user impact | Next business day | Alert noise, logging issues |\n\n## Critical Note\nOpenEvidence outages may affect clinical decision-making. Always communicate clearly with clinical staff, ensure fallback procedures are known, and document any clinical impact.\n\n## Instructions\n\n### Step 1: Initial Assessment (2 minutes)\nCheck OpenEvidence status page, your integration health endpoint, error rate metrics, and recent error logs.\n\n### Step 2: Follow Decision Tree\n- API errors + OpenEvidence status incident -> Enable fallback, wait for resolution\n- API errors + no status incident -> Check credentials, config, network\n- No API errors + unhealthy service -> Infrastructure issue (pods, memory, network)\n\n### Step 3: Apply Error-Specific Remediation\n- **401\u002F403**: Verify API key, rotate if needed, restart pods\n- **429**: Enable request queuing, contact OpenEvidence for limit increase\n- **500\u002F503**: Enable graceful degradation, notify clinical staff\n- **Timeout**: Increase timeout temporarily, check network latency\n\n### Step 4: Enable Fallback\nReturn helpful message directing to UpToDate, DynaMed, or clinical guidelines directly.\n\n### Step 5: Communicate\nNotify clinical staff via Slack\u002FTeams and email. Update status page.\n\n### Step 6: Post-Incident\nCollect evidence (logs, metrics, alerts), run postmortem with clinical impact assessment, create action items.\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## Error Handling\n| Error Type | Quick Fix |\n|------------|-----------|\n| 401\u002F403 Auth | `kubectl create secret` with new key, `kubectl rollout restart` |\n| 429 Rate Limit | `kubectl set env RATE_LIMIT_MODE=queue` |\n| 500\u002F503 Server | `kubectl set env OPENEVIDENCE_FALLBACK=true` |\n| Timeout | `kubectl set env OPENEVIDENCE_TIMEOUT=60000` |\n\n## Examples\n\n### One-Line Health Check\n```bash\nset -euo pipefail\ncurl -sf https:\u002F\u002Fapi.yourhealthcare.com\u002Fhealth\u002Fopenevidence | jq '.status' || echo \"UNHEALTHY\"\n```\n\n### Enable\u002FDisable Fallback\n```bash\nset -euo pipefail\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=true   # Enable\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=false  # Disable\n```\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for advanced patterns.\n\n## Resources\n- [OpenEvidence Status](https:\u002F\u002Fstatus.openevidence.com\u002F)\n- [OpenEvidence Support](mailto:support@openevidence.com)","# OpenEvidence Incident Runbook\n\n## Table of Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nRapid incident response procedures for OpenEvidence clinical AI integration outages in healthcare environments. Includes severity classification, triage steps, error-specific remediation, fallback procedures, and postmortem templates.\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\n## Severity Levels\n\n| Level | Definition | Response Time | Examples |\n|-------|------------|---------------|----------|\n| P1 | Complete outage | \u003C 15 min | API unreachable, all queries failing |\n| P2 | Degraded service | \u003C 1 hour | High latency, partial failures |\n| P3 | Minor impact | \u003C 4 hours | DeepConsult delays, webhook issues |\n| P4 | No user impact | Next business day | Alert noise, logging issues |\n\n## Critical Note\nOpenEvidence outages may affect clinical decision-making. Always communicate clearly with clinical staff, ensure fallback procedures are known, and document any clinical impact.\n\n## Instructions\n\n### Step 1: Initial Assessment (2 minutes)\nCheck OpenEvidence status page, your integration health endpoint, error rate metrics, and recent error logs.\n\n### Step 2: Follow Decision Tree\n- API errors + OpenEvidence status incident -> Enable fallback, wait for resolution\n- API errors + no status incident -> Check credentials, config, network\n- No API errors + unhealthy service -> Infrastructure issue (pods, memory, network)\n\n### Step 3: Apply Error-Specific Remediation\n- **401\u002F403**: Verify API key, rotate if needed, restart pods\n- **429**: Enable request queuing, contact OpenEvidence for limit increase\n- **500\u002F503**: Enable graceful degradation, notify clinical staff\n- **Timeout**: Increase timeout temporarily, check network latency\n\n### Step 4: Enable Fallback\nReturn helpful message directing to UpToDate, DynaMed, or clinical guidelines directly.\n\n### Step 5: Communicate\nNotify clinical staff via Slack\u002FTeams and email. Update status page.\n\n### Step 6: Post-Incident\nCollect evidence (logs, metrics, alerts), run postmortem with clinical impact assessment, create action items.\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## Error Handling\n| Error Type | Quick Fix |\n|------------|-----------|\n| 401\u002F403 Auth | `kubectl create secret` with new key, `kubectl rollout restart` |\n| 429 Rate Limit | `kubectl set env RATE_LIMIT_MODE=queue` |\n| 500\u002F503 Server | `kubectl set env OPENEVIDENCE_FALLBACK=true` |\n| Timeout | `kubectl set env OPENEVIDENCE_TIMEOUT=60000` |\n\n## Examples\n\n### One-Line Health Check\n```bash\nset -euo pipefail\ncurl -sf https:\u002F\u002Fapi.yourhealthcare.com\u002Fhealth\u002Fopenevidence | jq '.status' || echo \"UNHEALTHY\"\n```\n\n### Enable\u002FDisable Fallback\n```bash\nset -euo pipefail\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=true   # Enable\nkubectl set env deployment\u002Fclinical-evidence-api OPENEVIDENCE_FALLBACK=false  # Disable\n```\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for advanced patterns.\n\n## Resources\n- [OpenEvidence Status](https:\u002F\u002Fstatus.openevidence.com\u002F)\n- [OpenEvidence Support](mailto:support@openevidence.com)",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"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:*)","claude-code, codex, openclaw","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill openevidence-incident-runbook",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill openevidence-incident-runbook",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill openevidence-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fopenevidence-incident-runbook\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fimplementation.md","REFERENCE","参考文档",2106,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fopenevidence-incident-runbook\u002Freferences\u002Fimplementation.md",[56,63,70,77,84,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]