[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754V2Y68RHDDBCP1JP85A6P":3,"skill-same:01M754V2Y68RHDDBCP1JP85A6P":49},{"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},"01M754V2Y68RHDDBCP1JP85A6P","openevidence-prod-checklist",null,"Production readiness checklist for OpenEvidence clinical AI deployments.\nUse when preparing for production launch, conducting pre-deployment reviews,\nor auditing OpenEvidence integration for compliance.\nTrigger with phrases like \"openevidence production\", \"openevidence go-live\",\n\"openevidence checklist\", \"deploy openevidence\", \"openevidence readiness\".","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-prod-checklist\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: openevidence-prod-checklist\ndescription: |\n  Production readiness checklist for OpenEvidence clinical AI deployments.\n  Use when preparing for production launch, conducting pre-deployment reviews,\n  or auditing OpenEvidence integration for compliance.\n  Trigger with phrases like \"openevidence production\", \"openevidence go-live\",\n  \"openevidence checklist\", \"deploy openevidence\", \"openevidence readiness\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# OpenEvidence Production Checklist\n\n## Overview\nComprehensive checklist for deploying OpenEvidence clinical AI integrations to production healthcare environments.\n\n## Prerequisites\n- Completed development and testing phases\n- Signed BAA with OpenEvidence\n- Security review completed\n- Compliance team sign-off\n\n## Production Readiness Checklist\n\n### 1. Legal & Compliance\n\n- [ ] **Business Associate Agreement (BAA) signed**\n  - Contact: compliance@openevidence.com\n  - Required for any PHI handling\n\n- [ ] **API Terms of Service accepted**\n  - Review: https:\u002F\u002Fwww.openevidence.com\u002Fpolicies\u002Fapi\n\n- [ ] **Clinical use disclaimers in place**\n  - All clinical outputs must include appropriate disclaimers\n  - \"For informational purposes only. Verify with current guidelines.\"\n\n- [ ] **Liability and malpractice considerations reviewed**\n  - Legal review of clinical decision support usage\n\n- [ ] **Data processing agreement documented**\n  - What data is sent, stored, processed\n\n### 2. Security\n\n- [ ] **Production API keys generated**\n  - Separate keys from development\u002Fstaging\n  - Stored in secret manager (not environment variables)\n\n- [ ] **Key rotation schedule established**\n  - Recommend: 90-day rotation cycle\n\n- [ ] **IP allowlist configured** (if available)\n  - Restrict API access to known IP ranges\n\n- [ ] **TLS 1.2+ enforced**\n  - No fallback to older protocols\n\n- [ ] **PHI sanitization implemented**\n  - Review `openevidence-security-basics`\n\n- [ ] **Webhook signature verification active**\n  - All webhook endpoints validate signatures\n\n- [ ] **Audit logging enabled**\n  - HIPAA-compliant access logging\n  - Minimum 6-year retention\n\n### 3. Infrastructure\n\n- [ ] **High availability configuration**\n  ```typescript\n  \u002F\u002F Multiple API endpoints for failover\n  const config = {\n    primaryEndpoint: 'https:\u002F\u002Fapi.openevidence.com',\n    fallbackEndpoint: 'https:\u002F\u002Fapi-fallback.openevidence.com',\n    timeout: 30000,\n    retries: 3,\n  };\n  ```\n\n- [ ] **Circuit breaker implemented**\n  ```typescript\n  import CircuitBreaker from 'opossum';\n\n  const breaker = new CircuitBreaker(clinicalQuery, {\n    timeout: 30000,\n    errorThresholdPercentage: 50,\n    resetTimeout: 30000,\n  });\n  ```\n\n- [ ] **Rate limit handling configured**\n  - Review `openevidence-rate-limits`\n  - Request queuing for traffic spikes\n\n- [ ] **Timeout configuration appropriate**\n  - Clinical queries: 15-30s\n  - DeepConsult: 5-10 minutes\n\n- [ ] **Health check endpoint implemented**\n  ```typescript\n  app.get('\u002Fhealth\u002Fopenevidence', async (req, res) => {\n    try {\n      await client.health.check();\n      res.json({ status: 'healthy' });\n    } catch (error) {\n      res.status(503).json({ status: 'unhealthy', error: error.message });\n    }\n  });\n  ```\n\n### 4. Monitoring & Alerting\n\n- [ ] **Metrics collection active**\n  - Request count, latency, error rate\n  - Review `openevidence-observability`\n\n- [ ] **Alert rules configured**\n  | Alert | Threshold | Severity |\n  |-------|-----------|----------|\n  | Error rate > 5% | 5 min window | Warning |\n  | Error rate > 20% | 5 min window | Critical |\n  | P95 latency > 15s | 5 min window | Warning |\n  | Health check failed | 2 consecutive | Critical |\n\n- [ ] **Dashboard created**\n  - Real-time visibility into OpenEvidence integration health\n\n- [ ] **Log aggregation configured**\n  - Centralized logging for debugging\n  - PHI excluded from logs\n\n### 5. Error Handling & Resilience\n\n- [ ] **Graceful degradation implemented**\n  ```typescript\n  async function clinicalQueryWithFallback(question: string) {\n    try {\n      return await openEvidenceQuery(question);\n    } catch (error) {\n      \u002F\u002F Log error, alert, return cached or default response\n      await alertService.send('OpenEvidence unavailable');\n      return {\n        answer: 'Clinical evidence service temporarily unavailable. Please consult current guidelines directly.',\n        fallback: true,\n      };\n    }\n  }\n  ```\n\n- [ ] **Retry logic tested**\n  - Exponential backoff with jitter\n  - Respects Retry-After headers\n\n- [ ] **Error classification implemented**\n  - Review `openevidence-common-errors`\n\n### 6. Performance\n\n- [ ] **Response caching strategy**\n  - Cache frequently queried clinical information\n  - Cache TTL appropriate for clinical data freshness\n\n- [ ] **Connection pooling configured**\n  - Reuse HTTP connections\n\n- [ ] **Query optimization reviewed**\n  - Clear, specific clinical questions\n  - Appropriate context provided\n\n- [ ] **Load testing completed**\n  - Test at 2x expected peak traffic\n  - Verify rate limits not exceeded\n\n### 7. Documentation & Training\n\n- [ ] **Runbook created**\n  - Incident response procedures\n  - Review `openevidence-incident-runbook`\n\n- [ ] **On-call training completed**\n  - Team knows how to triage OpenEvidence issues\n\n- [ ] **User documentation updated**\n  - How to use clinical decision support\n  - Limitations and appropriate use\n\n- [ ] **Clinical staff training**\n  - Understanding AI-assisted decision support\n  - When to rely on vs. question AI recommendations\n\n### 8. Testing & Validation\n\n- [ ] **Integration tests passing**\n  - Against sandbox environment\n\n- [ ] **End-to-end tests passing**\n  - Full workflow validation\n\n- [ ] **Clinical validation completed**\n  - Sample queries reviewed by clinical team\n  - Responses appropriate and accurate\n\n- [ ] **Performance benchmarks met**\n  - P50 \u003C 5s, P95 \u003C 15s for clinical queries\n  - P50 \u003C 3min, P95 \u003C 5min for DeepConsult\n\n### 9. Deployment\n\n- [ ] **Blue-green or canary deployment planned**\n  - Gradual rollout with monitoring\n\n- [ ] **Rollback procedure documented**\n  - Quick revert if issues detected\n\n- [ ] **Feature flags configured**\n  - Ability to disable OpenEvidence quickly\n\n- [ ] **Database migrations completed**\n  - Audit log tables, cache tables ready\n\n### 10. Post-Launch\n\n- [ ] **Monitoring dashboard reviewed daily** (first week)\n\n- [ ] **Error reports triaged immediately**\n\n- [ ] **User feedback collection active**\n\n- [ ] **Performance baseline established**\n\n## Production Configuration Example\n\n```typescript\n\u002F\u002F config\u002Fopenevidence.production.ts\nexport const productionConfig = {\n  \u002F\u002F Credentials from secret manager\n  credentials: {\n    source: 'secret-manager',\n    apiKeyPath: 'projects\u002Fprod\u002Fsecrets\u002Fopenevidence-api-key',\n    orgIdPath: 'projects\u002Fprod\u002Fsecrets\u002Fopenevidence-org-id',\n  },\n\n  \u002F\u002F Endpoints\n  api: {\n    baseUrl: 'https:\u002F\u002Fapi.openevidence.com',\n    timeout: 30000,  # 30000: 30 seconds in ms\n    retries: 3,\n  },\n\n  \u002F\u002F Rate limiting\n  rateLimits: {\n    enabled: true,\n    maxConcurrent: 10,\n    requestsPerMinute: 100,\n  },\n\n  \u002F\u002F Circuit breaker\n  circuitBreaker: {\n    enabled: true,\n    errorThreshold: 50,\n    resetTimeout: 30000,  # 30 seconds in ms\n  },\n\n  \u002F\u002F Caching\n  cache: {\n    enabled: true,\n    ttlSeconds: 3600,  # 3600: timeout: 1 hour\n    maxEntries: 10000,  # 10000: 10 seconds in ms\n  },\n\n  \u002F\u002F Monitoring\n  monitoring: {\n    metricsEnabled: true,\n    tracingEnabled: true,\n    logLevel: 'info',\n  },\n};\n```\n\n## Output\n- Completed production readiness checklist\n- Configuration validated\n- All stakeholders signed off\n- Go-live approved\n\n## Resources\n- [OpenEvidence](https:\u002F\u002Fwww.openevidence.com\u002F)\n- [OpenEvidence Security](https:\u002F\u002Fwww.openevidence.com\u002Fsecurity)\n\n## Next Steps\nFor version upgrades, see `openevidence-upgrade-migration`.\n\n## Instructions\n\n1. Assess the current state of the deployment configuration\n2. Identify the specific requirements and constraints\n3. Apply the recommended patterns from this skill\n4. Validate the changes against expected behavior\n5. Document the configuration for team reference\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with deployment |\n| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |\n| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |\n\n## Examples\n\n**Basic usage**: Apply openevidence prod checklist to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize openevidence prod checklist for production environments with multiple constraints and team-specific requirements.","# OpenEvidence Production Checklist\n\n## Overview\nComprehensive checklist for deploying OpenEvidence clinical AI integrations to production healthcare environments.\n\n## Prerequisites\n- Completed development and testing phases\n- Signed BAA with OpenEvidence\n- Security review completed\n- Compliance team sign-off\n\n## Production Readiness Checklist\n\n### 1. Legal & Compliance\n\n- [ ] **Business Associate Agreement (BAA) signed**\n  - Contact: compliance@openevidence.com\n  - Required for any PHI handling\n\n- [ ] **API Terms of Service accepted**\n  - Review: https:\u002F\u002Fwww.openevidence.com\u002Fpolicies\u002Fapi\n\n- [ ] **Clinical use disclaimers in place**\n  - All clinical outputs must include appropriate disclaimers\n  - \"For informational purposes only. Verify with current guidelines.\"\n\n- [ ] **Liability and malpractice considerations reviewed**\n  - Legal review of clinical decision support usage\n\n- [ ] **Data processing agreement documented**\n  - What data is sent, stored, processed\n\n### 2. Security\n\n- [ ] **Production API keys generated**\n  - Separate keys from development\u002Fstaging\n  - Stored in secret manager (not environment variables)\n\n- [ ] **Key rotation schedule established**\n  - Recommend: 90-day rotation cycle\n\n- [ ] **IP allowlist configured** (if available)\n  - Restrict API access to known IP ranges\n\n- [ ] **TLS 1.2+ enforced**\n  - No fallback to older protocols\n\n- [ ] **PHI sanitization implemented**\n  - Review `openevidence-security-basics`\n\n- [ ] **Webhook signature verification active**\n  - All webhook endpoints validate signatures\n\n- [ ] **Audit logging enabled**\n  - HIPAA-compliant access logging\n  - Minimum 6-year retention\n\n### 3. Infrastructure\n\n- [ ] **High availability configuration**\n  ```typescript\n  \u002F\u002F Multiple API endpoints for failover\n  const config = {\n    primaryEndpoint: 'https:\u002F\u002Fapi.openevidence.com',\n    fallbackEndpoint: 'https:\u002F\u002Fapi-fallback.openevidence.com',\n    timeout: 30000,\n    retries: 3,\n  };\n  ```\n\n- [ ] **Circuit breaker implemented**\n  ```typescript\n  import CircuitBreaker from 'opossum';\n\n  const breaker = new CircuitBreaker(clinicalQuery, {\n    timeout: 30000,\n    errorThresholdPercentage: 50,\n    resetTimeout: 30000,\n  });\n  ```\n\n- [ ] **Rate limit handling configured**\n  - Review `openevidence-rate-limits`\n  - Request queuing for traffic spikes\n\n- [ ] **Timeout configuration appropriate**\n  - Clinical queries: 15-30s\n  - DeepConsult: 5-10 minutes\n\n- [ ] **Health check endpoint implemented**\n  ```typescript\n  app.get('\u002Fhealth\u002Fopenevidence', async (req, res) => {\n    try {\n      await client.health.check();\n      res.json({ status: 'healthy' });\n    } catch (error) {\n      res.status(503).json({ status: 'unhealthy', error: error.message });\n    }\n  });\n  ```\n\n### 4. Monitoring & Alerting\n\n- [ ] **Metrics collection active**\n  - Request count, latency, error rate\n  - Review `openevidence-observability`\n\n- [ ] **Alert rules configured**\n  | Alert | Threshold | Severity |\n  |-------|-----------|----------|\n  | Error rate > 5% | 5 min window | Warning |\n  | Error rate > 20% | 5 min window | Critical |\n  | P95 latency > 15s | 5 min window | Warning |\n  | Health check failed | 2 consecutive | Critical |\n\n- [ ] **Dashboard created**\n  - Real-time visibility into OpenEvidence integration health\n\n- [ ] **Log aggregation configured**\n  - Centralized logging for debugging\n  - PHI excluded from logs\n\n### 5. Error Handling & Resilience\n\n- [ ] **Graceful degradation implemented**\n  ```typescript\n  async function clinicalQueryWithFallback(question: string) {\n    try {\n      return await openEvidenceQuery(question);\n    } catch (error) {\n      \u002F\u002F Log error, alert, return cached or default response\n      await alertService.send('OpenEvidence unavailable');\n      return {\n        answer: 'Clinical evidence service temporarily unavailable. Please consult current guidelines directly.',\n        fallback: true,\n      };\n    }\n  }\n  ```\n\n- [ ] **Retry logic tested**\n  - Exponential backoff with jitter\n  - Respects Retry-After headers\n\n- [ ] **Error classification implemented**\n  - Review `openevidence-common-errors`\n\n### 6. Performance\n\n- [ ] **Response caching strategy**\n  - Cache frequently queried clinical information\n  - Cache TTL appropriate for clinical data freshness\n\n- [ ] **Connection pooling configured**\n  - Reuse HTTP connections\n\n- [ ] **Query optimization reviewed**\n  - Clear, specific clinical questions\n  - Appropriate context provided\n\n- [ ] **Load testing completed**\n  - Test at 2x expected peak traffic\n  - Verify rate limits not exceeded\n\n### 7. Documentation & Training\n\n- [ ] **Runbook created**\n  - Incident response procedures\n  - Review `openevidence-incident-runbook`\n\n- [ ] **On-call training completed**\n  - Team knows how to triage OpenEvidence issues\n\n- [ ] **User documentation updated**\n  - How to use clinical decision support\n  - Limitations and appropriate use\n\n- [ ] **Clinical staff training**\n  - Understanding AI-assisted decision support\n  - When to rely on vs. question AI recommendations\n\n### 8. Testing & Validation\n\n- [ ] **Integration tests passing**\n  - Against sandbox environment\n\n- [ ] **End-to-end tests passing**\n  - Full workflow validation\n\n- [ ] **Clinical validation completed**\n  - Sample queries reviewed by clinical team\n  - Responses appropriate and accurate\n\n- [ ] **Performance benchmarks met**\n  - P50 \u003C 5s, P95 \u003C 15s for clinical queries\n  - P50 \u003C 3min, P95 \u003C 5min for DeepConsult\n\n### 9. Deployment\n\n- [ ] **Blue-green or canary deployment planned**\n  - Gradual rollout with monitoring\n\n- [ ] **Rollback procedure documented**\n  - Quick revert if issues detected\n\n- [ ] **Feature flags configured**\n  - Ability to disable OpenEvidence quickly\n\n- [ ] **Database migrations completed**\n  - Audit log tables, cache tables ready\n\n### 10. Post-Launch\n\n- [ ] **Monitoring dashboard reviewed daily** (first week)\n\n- [ ] **Error reports triaged immediately**\n\n- [ ] **User feedback collection active**\n\n- [ ] **Performance baseline established**\n\n## Production Configuration Example\n\n```typescript\n\u002F\u002F config\u002Fopenevidence.production.ts\nexport const productionConfig = {\n  \u002F\u002F Credentials from secret manager\n  credentials: {\n    source: 'secret-manager',\n    apiKeyPath: 'projects\u002Fprod\u002Fsecrets\u002Fopenevidence-api-key',\n    orgIdPath: 'projects\u002Fprod\u002Fsecrets\u002Fopenevidence-org-id',\n  },\n\n  \u002F\u002F Endpoints\n  api: {\n    baseUrl: 'https:\u002F\u002Fapi.openevidence.com',\n    timeout: 30000,  # 30000: 30 seconds in ms\n    retries: 3,\n  },\n\n  \u002F\u002F Rate limiting\n  rateLimits: {\n    enabled: true,\n    maxConcurrent: 10,\n    requestsPerMinute: 100,\n  },\n\n  \u002F\u002F Circuit breaker\n  circuitBreaker: {\n    enabled: true,\n    errorThreshold: 50,\n    resetTimeout: 30000,  # 30 seconds in ms\n  },\n\n  \u002F\u002F Caching\n  cache: {\n    enabled: true,\n    ttlSeconds: 3600,  # 3600: timeout: 1 hour\n    maxEntries: 10000,  # 10000: 10 seconds in ms\n  },\n\n  \u002F\u002F Monitoring\n  monitoring: {\n    metricsEnabled: true,\n    tracingEnabled: true,\n    logLevel: 'info',\n  },\n};\n```\n\n## Output\n- Completed production readiness checklist\n- Configuration validated\n- All stakeholders signed off\n- Go-live approved\n\n## Resources\n- [OpenEvidence](https:\u002F\u002Fwww.openevidence.com\u002F)\n- [OpenEvidence Security](https:\u002F\u002Fwww.openevidence.com\u002Fsecurity)\n\n## Next Steps\nFor version upgrades, see `openevidence-upgrade-migration`.\n\n## Instructions\n\n1. Assess the current state of the deployment configuration\n2. Identify the specific requirements and constraints\n3. Apply the recommended patterns from this skill\n4. Validate the changes against expected behavior\n5. Document the configuration for team reference\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with deployment |\n| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |\n| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |\n\n## Examples\n\n**Basic usage**: Apply openevidence prod checklist to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize openevidence prod checklist for production environments with multiple constraints and team-specific requirements.",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Production readiness checklist for OpenEvidence clinical AI deployments.\nUse when preparing for production launch, conducting pre-deployment reviews,\nor auditing OpenEvidence integration for compliance.\nTrigger with phrases like \"openevidence production\", \"openevidence go-live\",\n\"openevidence checklist\", \"deploy openevidence\", \"openevidence readiness\".\n","Read, Grep","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-prod-checklist",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill openevidence-prod-checklist",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill openevidence-prod-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fopenevidence-prod-checklist\u002FSKILL.md",true,[],[50,57,64,71,78,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]