[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H85ZF87BK8EES3DF9PQ13M":3,"skill-same:01M6H85ZF87BK8EES3DF9PQ13M":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6H85ZF87BK8EES3DF9PQ13M","openevidence-deploy-integration",null,"Deploy OpenEvidence integrations to healthcare production environments.\nUse when deploying to production, setting up staging environments,\nor configuring cloud deployments for clinical AI applications.\nTrigger with phrases like \"deploy openevidence\", \"openevidence staging\",\n\"openevidence production deploy\", \"release openevidence\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fopenevidence-pack\u002Fskills\u002Fopenevidence-deploy-integration\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"deploy","openevidence deploy integration","integration","for","openclaw","environments","deploying to production","trigger","io","clinical","up","edit","write","read","integrations","Bash","healthcare","applications","release","code","2026-11-10 10:12:30",false,"---\nname: openevidence-deploy-integration\ndescription: |\n  Deploy OpenEvidence integrations to healthcare production environments.\n  Use when deploying to production, setting up staging environments,\n  or configuring cloud deployments for clinical AI applications.\n  Trigger with phrases like \"deploy openevidence\", \"openevidence staging\",\n  \"openevidence production deploy\", \"release openevidence\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# OpenEvidence Deploy Integration\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\nDeploy OpenEvidence clinical AI integrations to production healthcare environments with canary releases, Kubernetes manifests, health checks, and rollback procedures.\n\n## Prerequisites\n- CI pipeline configured (see `openevidence-ci-integration`)\n- Production credentials from OpenEvidence\n- Cloud platform configured (GCP, AWS, Azure)\n- Signed BAA for production environment\n\n## Instructions\n\n### Step 1: Multi-Environment Configuration\nDefine environment configs (dev\u002Fstaging\u002Fprod) with baseUrl, timeout, retries, secret paths, and feature flags.\n\n### Step 2: Create Deployment Workflow\nBuild GitHub Actions workflow with test -> build -> deploy-staging -> deploy-production stages. Use canary releases for production (no-traffic deploy, 10% canary, monitor, full rollout).\n\n### Step 3: Configure Kubernetes\nCreate Deployment (3 replicas), Service, Ingress, and HPA manifests. Use K8s secrets for API credentials, liveness\u002Freadiness probes against `\u002Fhealth`.\n\n### Step 4: Implement Health Checks\nCreate `\u002Fhealth` (basic) and `\u002Fhealth\u002Fopenevidence` (deep) endpoints that verify API connectivity and report latency.\n\n### Step 5: Prepare Rollback\nCreate rollback script that lists recent revisions, identifies previous, and shifts traffic back with health verification.\n\n## Output\n- Multi-environment deployment configuration\n- CI\u002FCD pipeline with canary releases\n- Kubernetes deployment manifests (Deployment, Service, Ingress, HPA)\n- Health check endpoints (basic + deep)\n- Rollback procedures and scripts\n\n## Error Handling\n| Deployment Issue | Detection | Resolution |\n|------------------|-----------|------------|\n| Health check fails | Readiness probe | Rollback to previous revision |\n| High error rate | Monitoring alert | Rollback, investigate logs |\n| Secret missing | Container fails to start | Check secret manager |\n| Rate limit hit | 429 errors spike | Scale down, check quotas |\n\n## Examples\n\n### Deploy to Staging\n```bash\ngcloud run deploy clinical-evidence-api-staging \\\n  --image $IMAGE --region us-central1 \\\n  --set-env-vars NODE_ENV=staging \\\n  --set-secrets OPENEVIDENCE_API_KEY=openevidence-staging-api-key:latest\n```\n\n### Rollback Production\n```bash\ngcloud run services update-traffic clinical-evidence-api \\\n  --region us-central1 --to-revisions PREVIOUS_REVISION=100\n```\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for advanced patterns.\n\n## Resources\n- [Cloud Run Documentation](https:\u002F\u002Fcloud.google.com\u002Frun\u002Fdocs)\n- [Kubernetes Deployments](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fworkloads\u002Fcontrollers\u002Fdeployment\u002F)","# OpenEvidence Deploy Integration\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\nDeploy OpenEvidence clinical AI integrations to production healthcare environments with canary releases, Kubernetes manifests, health checks, and rollback procedures.\n\n## Prerequisites\n- CI pipeline configured (see `openevidence-ci-integration`)\n- Production credentials from OpenEvidence\n- Cloud platform configured (GCP, AWS, Azure)\n- Signed BAA for production environment\n\n## Instructions\n\n### Step 1: Multi-Environment Configuration\nDefine environment configs (dev\u002Fstaging\u002Fprod) with baseUrl, timeout, retries, secret paths, and feature flags.\n\n### Step 2: Create Deployment Workflow\nBuild GitHub Actions workflow with test -> build -> deploy-staging -> deploy-production stages. Use canary releases for production (no-traffic deploy, 10% canary, monitor, full rollout).\n\n### Step 3: Configure Kubernetes\nCreate Deployment (3 replicas), Service, Ingress, and HPA manifests. Use K8s secrets for API credentials, liveness\u002Freadiness probes against `\u002Fhealth`.\n\n### Step 4: Implement Health Checks\nCreate `\u002Fhealth` (basic) and `\u002Fhealth\u002Fopenevidence` (deep) endpoints that verify API connectivity and report latency.\n\n### Step 5: Prepare Rollback\nCreate rollback script that lists recent revisions, identifies previous, and shifts traffic back with health verification.\n\n## Output\n- Multi-environment deployment configuration\n- CI\u002FCD pipeline with canary releases\n- Kubernetes deployment manifests (Deployment, Service, Ingress, HPA)\n- Health check endpoints (basic + deep)\n- Rollback procedures and scripts\n\n## Error Handling\n| Deployment Issue | Detection | Resolution |\n|------------------|-----------|------------|\n| Health check fails | Readiness probe | Rollback to previous revision |\n| High error rate | Monitoring alert | Rollback, investigate logs |\n| Secret missing | Container fails to start | Check secret manager |\n| Rate limit hit | 429 errors spike | Scale down, check quotas |\n\n## Examples\n\n### Deploy to Staging\n```bash\ngcloud run deploy clinical-evidence-api-staging \\\n  --image $IMAGE --region us-central1 \\\n  --set-env-vars NODE_ENV=staging \\\n  --set-secrets OPENEVIDENCE_API_KEY=openevidence-staging-api-key:latest\n```\n\n### Rollback Production\n```bash\ngcloud run services update-traffic clinical-evidence-api \\\n  --region us-central1 --to-revisions PREVIOUS_REVISION=100\n```\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for advanced patterns.\n\n## Resources\n- [Cloud Run Documentation](https:\u002F\u002Fcloud.google.com\u002Frun\u002Fdocs)\n- [Kubernetes Deployments](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fworkloads\u002Fcontrollers\u002Fdeployment\u002F)",{"name":5,"author":48,"license":14,"version":49,"description":50,"allowed-tools":51,"compatible-with":52},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Deploy OpenEvidence integrations to healthcare production environments.\nUse when deploying to production, setting up staging environments,\nor configuring cloud deployments for clinical AI applications.\nTrigger with phrases like \"deploy openevidence\", \"openevidence staging\",\n\"openevidence production deploy\", \"release openevidence\".\n","Read, Write, Edit, Bash(npm:*), Grep","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fopenevidence-pack\u002Fskills\u002Fopenevidence-deploy-integration",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add micsapp\u002Fmicstec-skills --skill openevidence-deploy-integration",{"tool":66,"command":67},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill openevidence-deploy-integration",{"tool":69,"command":70},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill openevidence-deploy-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fopenevidence-pack\u002Fskills\u002Fopenevidence-deploy-integration\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fimplementation.md","REFERENCE","参考文档",2228,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fopenevidence-pack\u002Fskills\u002Fopenevidence-deploy-integration\u002Freferences\u002Fimplementation.md",[81,115,142,163,183,207],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":95,"publishedAt":43},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[87,90],{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,26],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":127,"publishedAt":43},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[121,122,123,126],{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[128,129,130,131,97,132,42,133,134,135,136,137,105,106,112,138,139,113,140,141],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":43},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[148],{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},[150,151,152,153,97,100,105,106,154,155,156,157,158,159,160,113,161,162,141,26],"policy","authoring","apim policy authoring","security","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":171,"publishedAt":43},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[169,170],{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[172,153,173,105,157,174,97,128,175,176,177,178,106,179,113,180,181,182,114,26],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":43},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[190,191,192,130,193,194,195,196,105,197,198,199,34,200,201,202,203,204,205,206],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","list","view","project","project work","token","line","sprints",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":213,"publishedAt":43},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[209,214,215,216,217,218,219,155,220,221],"npm","js","calculate","node","math","user","compute","errors"]