[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71KCZM0FP3DCBQEV0YJQ7QZ":3,"skill-same:01M71KCZM0FP3DCBQEV0YJQ7QZ":86},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":75},"01M71KCZM0FP3DCBQEV0YJQ7QZ","supply-chain-security",null,"Use for software supply-chain security assessment covering SBOM, SCA, CI\u002FCD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.","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\u002Fsystems\u002Freverse-skill\u002Fskills\u002Fsupply-chain-security\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"supply chain security","chain security","supply","chain","supply chain","security","supply-chain","SCA","integrity","vulnerability","dependency","security assessment","images","SBOM","software","ci","CI\u002FCD","assessment","true","for","2026-11-10 10:12:30",false,"---\nname: supply-chain-security\ndescription: Use for software supply-chain security assessment covering SBOM, SCA, CI\u002FCD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.\nuser-invocable: true\n---\n# Supply Chain Security Testing\n\n## 适用场景\n\n- 软件供应链安全评估\n- 开源依赖漏洞扫描与验证\n- CI\u002FCD 管道安全审计\n- 容器镜像安全分析\n- 第三方组件合规审查\n- 构建产物溯源与完整性验证\n\n## 六层供应链治理框架\n\n```text\nLayer 1: 源码信任评估 → 上游仓库\u002F维护者\u002F发布历史审查\nLayer 2: 构建管道集成 → CI\u002FCD 安全门禁、签名验证\nLayer 3: 制品分发完整性 → 签名、校验和、SBOM 附加\nLayer 4: 运行时保护 → 容器扫描、准入控制\nLayer 5: 持续监控 → CVE 实时追踪、漏洞可达性分析\nLayer 6: 事件响应 → 供应链攻击应急、回滚策略\n```\n\n## 工作流\n\n### 1. SBOM 生成与审计\n\n```text\n生成 SBOM：\n□ CycloneDX 格式: cdxgen → bom.json\n□ SPDX 格式: sbom-tool generate\n□ Syft: syft \u003Cimage|dir> -o spdx-json\n\n审计要点：\n□ 是否存在未知\u002F未授权的依赖\n□ 是否存在已废弃\u002F停止维护的包\n□ 许可证冲突检测\n□ 直接依赖 vs 传递依赖清单\n□ 每个组件的发布时间线和维护者状态\n```\n\n### 2. 软件组成分析（SCA）\n\n```bash\n# OSV-Scanner（免费、Google 维护）\nosv-scanner scan -r . --format json\n\n# OWASP Dependency-Track（企业级持续监控）\ndocker run -p 8080:8080 dependencytrack\u002Fapiserver\n# → 上传 SBOM → 自动匹配 NVD\u002FOSV\u002FGitHub Advisory\n\n# Snyk（商业）\nsnyk test --all-projects\nsnyk monitor  # 持续监控\n\n# Trivy（容器 + 依赖 + IaC）\ntrivy fs .          # 文件系统扫描\ntrivy image nginx   # 容器镜像\ntrivy config .      # IaC 配置\n```\n\n### 3. 漏洞可达性验证\n\n```text\nSCA 告警 ≠ 实际风险！大多数 SCA 工具只有 ~15% 的告警是实际可达的。\n\n验证步骤：\n1. 用 Dependency-Track 或 Trivy 获取 CVE 列表\n2. 筛选 CVSS ≥ 7.0 的漏洞\n3. 对有 PoC 的 CVE 做可达性分析\n   - Code Property Graph 切片: 追踪用户输入到漏洞函数的路径\n   - DEPTEX 方法: EPD (Execution Path Dominance) + LLM 语义验证\n4. 在隔离环境中验证 PoC\n5. 对可达的漏洞按实际影响排序修复优先级\n```\n\n工具参考：\n- CodeQL: GitHub 代码查询 → 数据流分析\n- Snyk Code: 可达性标记\n- DEPTEX: LLM 辅助上下文感知风险评估\n\n### 4. CI\u002FCD 管道安全\n\n```text\n安全检查点：\n□ 代码提交 → pre-commit hook: gitleaks (密钥扫描)\n□ PR 阶段 → SCA 扫描 (Trivy\u002FOSV-Scanner)\n□ 构建阶段 → 制品签名 (cosign)\n□ 推送阶段 → SBOM 附加 (syft + attest)\n□ 部署阶段 → 准入控制 (OPA\u002FKyverno + 镜像扫描)\n□ 运行时 → 持续漏洞监控 (Dependency-Track)\n\n管道自身安全：\n□ Pipeline as Code 审计（GitHub Actions \u002F GitLab CI 配置注入）\n□ Runner 隔离（防止恶意构建突破容器）\n□ 密钥管理（Actions Secrets \u002F Vault，禁止硬编码）\n□ 第三方 Action 审查（锁定 commit SHA，非 tag）\n```\n\n### 5. 容器镜像安全\n\n```bash\n# Dockerfile 审计\nhadolint Dockerfile\n\n# 镜像扫描（多层：OS + 应用依赖 + 配置）\ntrivy image --severity HIGH,CRITICAL nginx:latest\n\n# 最小基础镜像\n# 优先: distroless → alpine → slim → 避免 latest\ndocker scout quickview nginx:latest\n\n# 镜像签名\ncosign sign --key cosign.key myimage:tag\ncosign verify --key cosign.pub myimage:tag\n```\n\n### 6. 第三方依赖审查\n\n```text\n新增依赖 Checklist：\n□ 维护状态：最近 6 个月有提交？维护者活跃度？\n□ 安全历史：过去有无被植入恶意代码？\n□ 依赖树：引入后新增多少传递依赖？\n□ 许可证：与项目许可证兼容？\n□ 替代方案：有无更安全的替代（Snyk Advisor \u002F Socket.dev 评分）？\n\n风险评估矩阵：\n  高维护 × 低依赖数 × 兼容许可证 → 低风险\n  低维护 × 高依赖数 × 许可证冲突 → 高风险\n```\n\n## 工具链\n\n| 工具 | 用途 | 获取 |\n|------|------|------|\n| OWASP Dependency-Track | 企业级持续 SCA | `docker pull dependencytrack\u002Fapiserver` |\n| OSV-Scanner | 免费 SCA（OSV.dev 生态） | `go install github.com\u002Fgoogle\u002Fosv-scanner` |\n| Trivy | 镜像 + 依赖 + IaC 扫描 | `apt install trivy` |\n| Syft | SBOM 生成 | `curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fsyft\u002Fmain\u002Finstall.sh` |\n| cdxgen | CycloneDX SBOM 生成 | `npm install -g @cyclonedx\u002Fcdxgen` |\n| Cosign | 容器签名 | `go install github.com\u002Fsigstore\u002Fcosign\u002Fv2\u002Fcmd\u002Fcosign` |\n| Gitleaks | 密钥\u002F凭证扫描 | `go install github.com\u002Fgitleaks\u002Fgitleaks\u002Fv8` |\n| Snyk | 商业 SCA + 可达性 | `npm install -g snyk` |\n| CodeQL | 代码查询 + 数据流 | GitHub Actions 内置 |\n\n## 参考\n\n- `references\u002Fsbom-sca-methodology.md` — SBOM + SCA 方法论\n- `references\u002Fcicd-pipeline-security.md` — CI\u002FCD 管道安全审计\n\n","# Supply Chain Security Testing\n\n## 适用场景\n\n- 软件供应链安全评估\n- 开源依赖漏洞扫描与验证\n- CI\u002FCD 管道安全审计\n- 容器镜像安全分析\n- 第三方组件合规审查\n- 构建产物溯源与完整性验证\n\n## 六层供应链治理框架\n\n```text\nLayer 1: 源码信任评估 → 上游仓库\u002F维护者\u002F发布历史审查\nLayer 2: 构建管道集成 → CI\u002FCD 安全门禁、签名验证\nLayer 3: 制品分发完整性 → 签名、校验和、SBOM 附加\nLayer 4: 运行时保护 → 容器扫描、准入控制\nLayer 5: 持续监控 → CVE 实时追踪、漏洞可达性分析\nLayer 6: 事件响应 → 供应链攻击应急、回滚策略\n```\n\n## 工作流\n\n### 1. SBOM 生成与审计\n\n```text\n生成 SBOM：\n□ CycloneDX 格式: cdxgen → bom.json\n□ SPDX 格式: sbom-tool generate\n□ Syft: syft \u003Cimage|dir> -o spdx-json\n\n审计要点：\n□ 是否存在未知\u002F未授权的依赖\n□ 是否存在已废弃\u002F停止维护的包\n□ 许可证冲突检测\n□ 直接依赖 vs 传递依赖清单\n□ 每个组件的发布时间线和维护者状态\n```\n\n### 2. 软件组成分析（SCA）\n\n```bash\n# OSV-Scanner（免费、Google 维护）\nosv-scanner scan -r . --format json\n\n# OWASP Dependency-Track（企业级持续监控）\ndocker run -p 8080:8080 dependencytrack\u002Fapiserver\n# → 上传 SBOM → 自动匹配 NVD\u002FOSV\u002FGitHub Advisory\n\n# Snyk（商业）\nsnyk test --all-projects\nsnyk monitor  # 持续监控\n\n# Trivy（容器 + 依赖 + IaC）\ntrivy fs .          # 文件系统扫描\ntrivy image nginx   # 容器镜像\ntrivy config .      # IaC 配置\n```\n\n### 3. 漏洞可达性验证\n\n```text\nSCA 告警 ≠ 实际风险！大多数 SCA 工具只有 ~15% 的告警是实际可达的。\n\n验证步骤：\n1. 用 Dependency-Track 或 Trivy 获取 CVE 列表\n2. 筛选 CVSS ≥ 7.0 的漏洞\n3. 对有 PoC 的 CVE 做可达性分析\n   - Code Property Graph 切片: 追踪用户输入到漏洞函数的路径\n   - DEPTEX 方法: EPD (Execution Path Dominance) + LLM 语义验证\n4. 在隔离环境中验证 PoC\n5. 对可达的漏洞按实际影响排序修复优先级\n```\n\n工具参考：\n- CodeQL: GitHub 代码查询 → 数据流分析\n- Snyk Code: 可达性标记\n- DEPTEX: LLM 辅助上下文感知风险评估\n\n### 4. CI\u002FCD 管道安全\n\n```text\n安全检查点：\n□ 代码提交 → pre-commit hook: gitleaks (密钥扫描)\n□ PR 阶段 → SCA 扫描 (Trivy\u002FOSV-Scanner)\n□ 构建阶段 → 制品签名 (cosign)\n□ 推送阶段 → SBOM 附加 (syft + attest)\n□ 部署阶段 → 准入控制 (OPA\u002FKyverno + 镜像扫描)\n□ 运行时 → 持续漏洞监控 (Dependency-Track)\n\n管道自身安全：\n□ Pipeline as Code 审计（GitHub Actions \u002F GitLab CI 配置注入）\n□ Runner 隔离（防止恶意构建突破容器）\n□ 密钥管理（Actions Secrets \u002F Vault，禁止硬编码）\n□ 第三方 Action 审查（锁定 commit SHA，非 tag）\n```\n\n### 5. 容器镜像安全\n\n```bash\n# Dockerfile 审计\nhadolint Dockerfile\n\n# 镜像扫描（多层：OS + 应用依赖 + 配置）\ntrivy image --severity HIGH,CRITICAL nginx:latest\n\n# 最小基础镜像\n# 优先: distroless → alpine → slim → 避免 latest\ndocker scout quickview nginx:latest\n\n# 镜像签名\ncosign sign --key cosign.key myimage:tag\ncosign verify --key cosign.pub myimage:tag\n```\n\n### 6. 第三方依赖审查\n\n```text\n新增依赖 Checklist：\n□ 维护状态：最近 6 个月有提交？维护者活跃度？\n□ 安全历史：过去有无被植入恶意代码？\n□ 依赖树：引入后新增多少传递依赖？\n□ 许可证：与项目许可证兼容？\n□ 替代方案：有无更安全的替代（Snyk Advisor \u002F Socket.dev 评分）？\n\n风险评估矩阵：\n  高维护 × 低依赖数 × 兼容许可证 → 低风险\n  低维护 × 高依赖数 × 许可证冲突 → 高风险\n```\n\n## 工具链\n\n| 工具 | 用途 | 获取 |\n|------|------|------|\n| OWASP Dependency-Track | 企业级持续 SCA | `docker pull dependencytrack\u002Fapiserver` |\n| OSV-Scanner | 免费 SCA（OSV.dev 生态） | `go install github.com\u002Fgoogle\u002Fosv-scanner` |\n| Trivy | 镜像 + 依赖 + IaC 扫描 | `apt install trivy` |\n| Syft | SBOM 生成 | `curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fsyft\u002Fmain\u002Finstall.sh` |\n| cdxgen | CycloneDX SBOM 生成 | `npm install -g @cyclonedx\u002Fcdxgen` |\n| Cosign | 容器签名 | `go install github.com\u002Fsigstore\u002Fcosign\u002Fv2\u002Fcmd\u002Fcosign` |\n| Gitleaks | 密钥\u002F凭证扫描 | `go install github.com\u002Fgitleaks\u002Fgitleaks\u002Fv8` |\n| Snyk | 商业 SCA + 可达性 | `npm install -g snyk` |\n| CodeQL | 代码查询 + 数据流 | GitHub Actions 内置 |\n\n## 参考\n\n- `references\u002Fsbom-sca-methodology.md` — SBOM + SCA 方法论\n- `references\u002Fcicd-pipeline-security.md` — CI\u002FCD 管道安全审计\n\n",{"name":5,"description":7,"user-invocable":52},true,"main","cd89f013b617f7eea982a9bbc60e992974fda2aa","systems\u002Freverse-skill\u002Fskills\u002Fsupply-chain-security",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":64,"prompt":74,"zipAvailable":52},[65,68,71],{"tool":66,"command":67},"npx","npx skills add coco-research\u002Fcoco --skill supply-chain-security",{"tool":69,"command":70},"bunx","bunx skills add coco-research\u002Fcoco --skill supply-chain-security",{"tool":72,"command":73},"pnpm","pnpm dlx skills add coco-research\u002Fcoco --skill supply-chain-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Freverse-skill\u002Fskills\u002Fsupply-chain-security\u002FSKILL.md",[76,82],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fcicd-pipeline-security.md","REFERENCE","参考文档",3489,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Freverse-skill\u002Fskills\u002Fsupply-chain-security\u002Freferences\u002Fcicd-pipeline-security.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fsbom-sca-methodology.md",2046,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Freverse-skill\u002Fskills\u002Fsupply-chain-security\u002Freferences\u002Fsbom-sca-methodology.md",[87,112,122,140,175,194],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":94,"publishedAt":47},"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",[93],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"super","trading super intelligence","intelligence","trading","validator","personas","local","composites","studio","team","across","world","first","gated","2026","lm studio","local-first",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":47},"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",[118],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[120,95,121,97,99,100,101,102,103,104,105,106,107,108,109,110,111],"strategy","strategy super intelligence",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":134,"publishedAt":47},"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",[128,129],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[135,95,136,137,138,97,99,100,101,102,139,103,104,105,106,107,108,109,110,111],"risk","risk compliance super intelligence","compliance","risk compliance","grc",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":159,"publishedAt":47},"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",[146,149,152,153,156],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":154,"categoryName":155,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":157,"categoryName":158,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000032","设计师",[160,161,97,162,95,163,164,165,166,167,168,104,105,169,170,109,171,172,173,174],"design","product","product design","product design super intelligence","foundations","product-design","decision","design systems","usability","leadership","ux","brain","craft","metrics","trust",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":183,"publishedAt":47},"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",[181,182],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},[184,95,185,97,186,187,174,188,100,189,190,191,120,104,105,192,137,193,109,171],"ip","legal ip super intelligence","legal","sep","tech","litigation","ai governance","open","open-source","governance",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":47},"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",[200],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[202,95,203,204,97,187,174,205,206,100,207,208,120,104,105,209,210,211,212,109],"healthcare","healthcare life sciences super intelligence","life","economics","discovery","policy","clinical","clinical trials","health","trials","genomics"]