[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JVMAD40AA7R7J8Q5AF6EG":3,"skill-same:01M71JVMAD40AA7R7J8Q5AF6EG":80},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M71JVMAD40AA7R7J8Q5AF6EG","pmstudio-dr",null,"Generate a Disaster Recovery plan with RTO\u002FRPO targets. Use when someone asks to \"create a DR plan\", \"disaster recovery\", \"business continuity\", or \"RTO RPO\". Do NOT use for step-by-step restoration runbooks — use \u002Fpmstudio-recovery instead. Designed for SaaS platform products where Coco Inc is the customer — focuses on service continuity, data recovery, and vendor dependency management rather than infrastructure rebuild.","coco-research\u002Fcoco","coco-research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68911604?v=4","01M71JRE9C4NM4NSZM4JD0BJTB","Coco Research","01M71JREA0ZMR0PMH3CKA99SN1",631,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fdr-plan\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"dr","pmstudio dr","platform","do","infrastructure","data","rpo","rto","dependency","customer","generate","plan","recovery plan","create","rebuild","when","continuity","runbooks","business continuity","dr plan","2026-11-10 10:12:30",false,"---\nname: pmstudio-dr\ndescription: Generate a Disaster Recovery plan with RTO\u002FRPO targets. Use when someone asks to \"create a DR plan\", \"disaster recovery\", \"business continuity\", or \"RTO RPO\". Do NOT use for step-by-step restoration runbooks — use \u002Fpmstudio-recovery instead. Designed for SaaS platform products where Coco Inc is the customer — focuses on service continuity, data recovery, and vendor dependency management rather than infrastructure rebuild.\ndomain: ops\n---\n\n# DR Plan — Disaster Recovery Plan\n\n## Purpose\n\nGenerates a Disaster Recovery plan scoped to a specific product. For SaaS products (where the vendor owns infrastructure), this plan focuses on what Coco Inc controls: data exports, integration failover, access recovery, communication, and business continuity.\n\n## Process\n\n### Step 1: Read Context\n\n**Read all that exist:**\n- `CLAUDE.local.md` — architecture, integrations, vendor info, data strategy\n- `PRD\u002F*.html` or `PRD\u002F*.md` — NFRs, technical considerations, integrations, data architecture\n- `Architecture\u002F` — system diagrams, data flows\n- `Operational\u002FIRP-*.html` — incident response plan (if exists, reference for communication)\n\n### Step 2: Determine Product Type\n\nFrom context, classify the product:\n\n| Type | DR Focus | Example |\n|------|----------|---------|\n| **SaaS (customer)** | Vendor dependency, data portability, alternative workflows | (third-party SaaS)  |\n| **Self-hosted** | Infrastructure recovery, backup\u002Frestore, failover | Custom app on EKS |\n| **Hybrid** | Both vendor and self-hosted components | SaaS + custom middleware |\n\nAdjust the plan scope accordingly. For SaaS, skip infrastructure sections (that's the vendor's problem). Add vendor SLA and data portability sections.\n\n### Step 3: Ask Discovery Questions\n\nOnly ask what can't be inferred:\n\n1. **Business criticality tier?** (Tier 1 critical \u002F Tier 2 important \u002F Tier 3 standard)\n2. **What's the maximum tolerable downtime?** (This becomes RTO)\n3. **What's the maximum tolerable data loss?** (This becomes RPO)\n4. **Are there manual workarounds if the product is down?** (e.g., \"we can use Excel for 48 hours\")\n5. **Vendor SLA?** (uptime commitment, support response times, data export capabilities)\n6. **Backup strategy?** (Does data export to Snowflake\u002FSharePoint? How often?)\n\n### Step 4: Generate DR Plan\n\n**Output:** `Operational\u002FDR-Plan-{ProductName}-{Date}.html`\n\nSelf-contained HTML with clean typography and print CSS.\n\n**11 sections:**\n\n**1. Purpose & Scope**\n- Product name, ProdID, instances covered\n- What this plan covers and doesn't cover\n- Relationship to vendor's own DR plan\n\n**2. Service Classification**\n- Business criticality tier with justification\n- Data classification (Purple\u002FRed\u002FYellow\u002FGreen)\n- Regulatory or compliance requirements affecting recovery\n- Business impact of downtime (per hour\u002Fday)\n\n**3. RTO\u002FRPO Targets**\n\nPer-component target table:\n\n| Component | RTO | RPO | Justification |\n|-----------|-----|-----|---------------|\n| Core platform | 4 hours | 24 hours | Vendor SLA: 99.9% uptime |\n| Data in Snowflake | 2 hours | 0 (real-time sync) | Analytics feeds downstream |\n| Integrations (SSO) | 1 hour | N\u002FA | Users locked out |\n| Integrations (ServiceNow) | 8 hours | N\u002FA | Ticket creation manual fallback |\n\n**4. Disaster Scenarios**\n\nRanked by likelihood x impact:\n\n1. **Vendor platform outage** (most likely) — vendor is down, product inaccessible\n2. **Data corruption** — bad data entered or sync error corrupts records\n3. **Access loss** — SSO failure, license revocation, permission misconfiguration\n4. **Integration failure** — upstream\u002Fdownstream system breaks connection\n5. **Security breach** — unauthorized access, data exfiltration\n6. **Vendor business failure** — vendor acquired, shut down, or ends product\n\nFor each scenario: description, likelihood, impact, detection method.\n\n**5. Recovery Procedures**\n\nPer-scenario step-by-step. See `references\u002Fsaas-dr-patterns.md` for SaaS-specific recovery patterns.\n\nStructure per scenario:\n- Trigger condition (how do we know this is happening)\n- Immediate actions (first 15 minutes)\n- Short-term recovery (first 4 hours)\n- Full recovery (to meet RTO)\n- Verification checklist\n\n**6. Communication Plan**\n- Who to notify per scenario and severity\n- Templates (reference IRP if it exists, or provide standalone)\n- Vendor communication (support ticket + account manager)\n- Stakeholder updates cadence during outage\n\n**7. Dependencies**\n- External systems required for recovery\n- Vendor contacts (support, account manager, escalation)\n- SLA commitments and how to invoke them\n- Third-party services (SSO provider, email, etc.)\n\n**8. Data Backup & Restoration**\n- What data is backed up (by vendor, by Coco Inc)\n- Backup frequency and retention\n- Where backups are stored\n- Restoration procedure (step-by-step)\n- Data validation after restoration\n\n**9. Manual Workarounds**\n- What business processes can continue without the product\n- Excel\u002FSharePoint fallback procedures\n- Duration the workaround is sustainable\n- Data reconciliation procedure when product is restored\n\n**10. Testing Schedule**\n- DR test cadence (annually minimum, semi-annually recommended)\n- Test scenarios (tabletop, partial recovery, full recovery)\n- Last test date and results\n- Next scheduled test\n- Test success criteria\n\n**11. Review & Maintenance**\n- Review cadence: semi-annually or after any DR event\n- Approval chain (PM, Security POC, Sponsor)\n- Version history\n- Distribution list\n\n### Step 5: Present for Review\n\nShow the plan outline with key decisions highlighted:\n- RTO\u002FRPO targets\n- Scenario prioritization\n- Manual workaround availability\n\nAsk for approval before writing.\n\n## Critical Rules\n\n1. **RTO\u002FRPO must be numbers, not words.** \"As fast as possible\" is not an RTO. Push for specific hours.\n2. **Vendor DR is not your DR.** The vendor's uptime SLA is an input to your plan, not a substitute for it. Your plan covers what happens on Coco Inc's side.\n3. **Manual workarounds are critical.** For every scenario, document what the business does while the product is down. If there's no workaround, that's a risk to flag.\n4. **Data portability is DR.** If you can't get data out of the product, you can't recover from vendor failure. Document export capabilities.\n5. **Test the plan.** A plan that's never been tested is a wish list. Include a testing schedule and success criteria.\n","# DR Plan — Disaster Recovery Plan\n\n## Purpose\n\nGenerates a Disaster Recovery plan scoped to a specific product. For SaaS products (where the vendor owns infrastructure), this plan focuses on what Coco Inc controls: data exports, integration failover, access recovery, communication, and business continuity.\n\n## Process\n\n### Step 1: Read Context\n\n**Read all that exist:**\n- `CLAUDE.local.md` — architecture, integrations, vendor info, data strategy\n- `PRD\u002F*.html` or `PRD\u002F*.md` — NFRs, technical considerations, integrations, data architecture\n- `Architecture\u002F` — system diagrams, data flows\n- `Operational\u002FIRP-*.html` — incident response plan (if exists, reference for communication)\n\n### Step 2: Determine Product Type\n\nFrom context, classify the product:\n\n| Type | DR Focus | Example |\n|------|----------|---------|\n| **SaaS (customer)** | Vendor dependency, data portability, alternative workflows | (third-party SaaS)  |\n| **Self-hosted** | Infrastructure recovery, backup\u002Frestore, failover | Custom app on EKS |\n| **Hybrid** | Both vendor and self-hosted components | SaaS + custom middleware |\n\nAdjust the plan scope accordingly. For SaaS, skip infrastructure sections (that's the vendor's problem). Add vendor SLA and data portability sections.\n\n### Step 3: Ask Discovery Questions\n\nOnly ask what can't be inferred:\n\n1. **Business criticality tier?** (Tier 1 critical \u002F Tier 2 important \u002F Tier 3 standard)\n2. **What's the maximum tolerable downtime?** (This becomes RTO)\n3. **What's the maximum tolerable data loss?** (This becomes RPO)\n4. **Are there manual workarounds if the product is down?** (e.g., \"we can use Excel for 48 hours\")\n5. **Vendor SLA?** (uptime commitment, support response times, data export capabilities)\n6. **Backup strategy?** (Does data export to Snowflake\u002FSharePoint? How often?)\n\n### Step 4: Generate DR Plan\n\n**Output:** `Operational\u002FDR-Plan-{ProductName}-{Date}.html`\n\nSelf-contained HTML with clean typography and print CSS.\n\n**11 sections:**\n\n**1. Purpose & Scope**\n- Product name, ProdID, instances covered\n- What this plan covers and doesn't cover\n- Relationship to vendor's own DR plan\n\n**2. Service Classification**\n- Business criticality tier with justification\n- Data classification (Purple\u002FRed\u002FYellow\u002FGreen)\n- Regulatory or compliance requirements affecting recovery\n- Business impact of downtime (per hour\u002Fday)\n\n**3. RTO\u002FRPO Targets**\n\nPer-component target table:\n\n| Component | RTO | RPO | Justification |\n|-----------|-----|-----|---------------|\n| Core platform | 4 hours | 24 hours | Vendor SLA: 99.9% uptime |\n| Data in Snowflake | 2 hours | 0 (real-time sync) | Analytics feeds downstream |\n| Integrations (SSO) | 1 hour | N\u002FA | Users locked out |\n| Integrations (ServiceNow) | 8 hours | N\u002FA | Ticket creation manual fallback |\n\n**4. Disaster Scenarios**\n\nRanked by likelihood x impact:\n\n1. **Vendor platform outage** (most likely) — vendor is down, product inaccessible\n2. **Data corruption** — bad data entered or sync error corrupts records\n3. **Access loss** — SSO failure, license revocation, permission misconfiguration\n4. **Integration failure** — upstream\u002Fdownstream system breaks connection\n5. **Security breach** — unauthorized access, data exfiltration\n6. **Vendor business failure** — vendor acquired, shut down, or ends product\n\nFor each scenario: description, likelihood, impact, detection method.\n\n**5. Recovery Procedures**\n\nPer-scenario step-by-step. See `references\u002Fsaas-dr-patterns.md` for SaaS-specific recovery patterns.\n\nStructure per scenario:\n- Trigger condition (how do we know this is happening)\n- Immediate actions (first 15 minutes)\n- Short-term recovery (first 4 hours)\n- Full recovery (to meet RTO)\n- Verification checklist\n\n**6. Communication Plan**\n- Who to notify per scenario and severity\n- Templates (reference IRP if it exists, or provide standalone)\n- Vendor communication (support ticket + account manager)\n- Stakeholder updates cadence during outage\n\n**7. Dependencies**\n- External systems required for recovery\n- Vendor contacts (support, account manager, escalation)\n- SLA commitments and how to invoke them\n- Third-party services (SSO provider, email, etc.)\n\n**8. Data Backup & Restoration**\n- What data is backed up (by vendor, by Coco Inc)\n- Backup frequency and retention\n- Where backups are stored\n- Restoration procedure (step-by-step)\n- Data validation after restoration\n\n**9. Manual Workarounds**\n- What business processes can continue without the product\n- Excel\u002FSharePoint fallback procedures\n- Duration the workaround is sustainable\n- Data reconciliation procedure when product is restored\n\n**10. Testing Schedule**\n- DR test cadence (annually minimum, semi-annually recommended)\n- Test scenarios (tabletop, partial recovery, full recovery)\n- Last test date and results\n- Next scheduled test\n- Test success criteria\n\n**11. Review & Maintenance**\n- Review cadence: semi-annually or after any DR event\n- Approval chain (PM, Security POC, Sponsor)\n- Version history\n- Distribution list\n\n### Step 5: Present for Review\n\nShow the plan outline with key decisions highlighted:\n- RTO\u002FRPO targets\n- Scenario prioritization\n- Manual workaround availability\n\nAsk for approval before writing.\n\n## Critical Rules\n\n1. **RTO\u002FRPO must be numbers, not words.** \"As fast as possible\" is not an RTO. Push for specific hours.\n2. **Vendor DR is not your DR.** The vendor's uptime SLA is an input to your plan, not a substitute for it. Your plan covers what happens on Coco Inc's side.\n3. **Manual workarounds are critical.** For every scenario, document what the business does while the product is down. If there's no workaround, that's a risk to flag.\n4. **Data portability is DR.** If you can't get data out of the product, you can't recover from vendor failure. Document export capabilities.\n5. **Test the plan.** A plan that's never been tested is a wish list. Include a testing schedule and success criteria.\n",{"name":5,"domain":49,"description":7},"ops","main","cd89f013b617f7eea982a9bbc60e992974fda2aa","skills\u002Fdr-plan",15,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco","https:\u002F\u002Fcocoresearch.org\u002Fcoco\u002F","https:\u002F\u002Fgithub.com\u002Fcoco-research","https:\u002F\u002Fcocoresearch.org","Local-first, open-source tools for people who work with AI agents: governed memory, agents that check their own work, and data that stays on your machine.","2026-11-11 12:18:13",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add coco-research\u002Fcoco --skill pmstudio-dr",{"tool":66,"command":67},"bunx","bunx skills add coco-research\u002Fcoco --skill pmstudio-dr",{"tool":69,"command":70},"pnpm","pnpm dlx skills add coco-research\u002Fcoco --skill pmstudio-dr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fdr-plan\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fsaas-dr-patterns.md","REFERENCE","参考文档",5751,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fdr-plan\u002Freferences\u002Fsaas-dr-patterns.md",[81,106,116,134,169,188],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":88,"publishedAt":44},"01M71KEJXF9KMT0BWCMRSRFA4M","trading-super-intelligence","Trading Super Intelligence Team. Named real-world personas across 8 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Ftrading\u002FSKILL.md",[87],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105],"super","trading super intelligence","intelligence","trading","validator","personas","local","composites","studio","team","across","world","first","gated","2026","lm studio","local-first",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":44},"01M71KEFWS3CMAP7DF1P0FWTDE","strategy-super-intelligence","Strategy Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fstrategy\u002FSKILL.md",[112],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[114,89,115,91,93,94,95,96,97,98,99,100,101,102,103,104,105],"strategy","strategy super intelligence",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":128,"publishedAt":44},"01M71KED56ZEPK2QE84QSQPMT0","risk-compliance-super-intelligence","Risk & Compliance (GRC) Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Frisk-compliance\u002FSKILL.md",[122,123],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[129,89,130,131,132,91,93,94,95,96,133,97,98,99,100,101,102,103,104,105],"risk","risk compliance super intelligence","compliance","risk compliance","grc",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":153,"publishedAt":44},"01M71KE9A2FWSC74VA96W1EZSN","product-design-super-intelligence","Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery\u002Fresearch, growth\u002Fmetrics, design foundations\u002Fusability, design leadership\u002Fcraft, UX\u002Fcontent, design systems, and a…","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fproduct-design\u002FSKILL.md",[140,143,146,147,150],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":144,"categoryName":145,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":148,"categoryName":149,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":151,"categoryName":152,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000032","设计师",[154,155,91,156,89,157,158,159,160,161,162,98,99,163,164,103,165,166,167,168],"design","product","product design","product design super intelligence","foundations","product-design","decision","design systems","usability","leadership","ux","brain","craft","metrics","trust",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":177,"publishedAt":44},"01M71KE6H9FPSD9TECYFBPXZ8Y","legal-ip-super-intelligence","Your legal, IP, and regulatory brain trust. 31 named personas across 7 cells covering patent strategy, tech licensing, regulatory litigation, AI governance, open-source compliance, privacy law, and antitrust.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Flegal-ip\u002FSKILL.md",[175,176],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},[178,89,179,91,180,181,168,182,94,183,184,185,114,98,99,186,131,187,103,165],"ip","legal ip super intelligence","legal","sep","tech","litigation","ai governance","open","open-source","governance",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":44},"01M71KE36QRY610V6YVB9JWRND","healthcare-life-sciences-super-intelligence","Your healthcare and life sciences brain trust. 25 named personas across 7 cells covering drug discovery, medtech, biotech strategy, health policy, genomics, clinical trials, and healthcare economics.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fhealthcare-life-sciences\u002FSKILL.md",[194],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[196,89,197,198,91,181,168,199,200,94,201,202,114,98,99,203,204,205,206,103],"healthcare","healthcare life sciences super intelligence","life","economics","discovery","policy","clinical","clinical trials","health","trials","genomics"]