[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JTXVFJDE26AB7AWN47B9Q":3,"skill-same:01M71JTXVFJDE26AB7AWN47B9Q":73},{"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":37,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M71JTXVFJDE26AB7AWN47B9Q","coco-ship",null,"Use when finished work needs to reach a coco-managed repository (coco-research\u002Fcoco or similar) — verifies branch state, commits, pushes through the corporate DLP guard only when actually needed, opens a PR against main, waits for CI, and reports the result. Never merges, never pushes to main directly.","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\u002Fcoco-ship\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],"coco ship","ship","guard","use","true","for","commits","pr","repository","result","work","reports","when","main","only","managed","ci","dlp","never","branch","2026-11-10 10:12:30",false,"---\nname: coco-ship\ndescription: Use when finished work needs to reach a coco-managed repository (coco-research\u002Fcoco or similar) — verifies branch state, commits, pushes through the corporate DLP guard only when actually needed, opens a PR against main, waits for CI, and reports the result. Never merges, never pushes to main directly.\ndomain: engineering\nuser-invocable: true\n---\n\n# Shipping to a CoCo-managed Repo\n\n## Overview\n\nFormalizes the branch → commit → guard-aware push → PR → CI-wait → report flow used for shipping\nwork to `coco-research\u002Fcoco` (or any repo carrying the same corporate git-guard pre-push hook), so it\ndoesn't have to be re-derived by hand each time.\n\n**Core principle:** Verify state → commit → detect whether the guard actually applies → confirm →\npush → open PR → wait for real CI → report. Never merge. Never push to `main` directly, regardless of\nhow it's asked.\n\n**Announce at start:** \"I'm using the coco-ship skill to ship this branch.\"\n\nThis is the direct formalization of Option 2 (\"Push and Create PR\") in\n`finishing-a-development-branch`, specialized for repos that carry the corporate git-guard. It\nassumes implementation is already done and reviewed — it doesn't replace planning skills like\n`brainstorming`, `writing-plans`, or GSD's phase workflow, and it doesn't run tests itself (that's\n`finishing-a-development-branch`'s Step 1, or the project's own CI).\n\n## The Process\n\n### Step 1: Preflight\n\n```bash\ngit status -sb\ngit branch --show-current\n```\n\n**If the current branch is `main` or `master`:** stop. Do not commit or push here. Offer to create a\nfeature branch first:\n\n```bash\ngit checkout -b \u003Cfeature-branch-name>\n```\n\n**If there's nothing to commit and the branch isn't already ahead of its upstream:** stop and say so\n— there's nothing to ship.\n\n### Step 2: Commit\n\nUse the standard git-commit protocol already in effect for this harness — this isn't a new\ninvention, just invoked from inside the skill:\n\n1. In parallel: `git status`, `git diff` (staged + unstaged), `git log` (recent messages, for style).\n2. Draft a commit message from the actual diff — why, not just what — matching the repo's existing\n   style.\n3. Stage named files explicitly. Never `git add -A` or `git add .`.\n4. Commit with a `Co-Authored-By` trailer, via a heredoc so formatting survives.\n5. `git status` again to confirm a clean tree.\n\nIf a pre-commit hook fails, fix the issue, re-stage, and create a **new** commit — never `--amend` a\ncommit that a failed hook means never actually landed.\n\n### Step 3: Detect whether the guard bypass is actually needed\n\nDon't assume — check:\n\n```bash\ngit remote -v\ngh repo view \u003Cowner>\u002F\u003Crepo> --json visibility,owner -q '\"\\(.visibility) \\(.owner.login)\"'\ngit config --show-origin --get core.hooksPath\n```\n\nA `GIT_GUARD_REASON` bypass is only needed when the repo is `PUBLIC` **and** the owner isn't on the\nguard's allowlist — check the actual guard config or ask the user which org(s) it allows, rather than\nassuming. If `core.hooksPath` doesn't point at the guard, don't assume a bypass is relevant on this\nmachine at all — say so.\n\n### Step 4: Confirm — every time, no exceptions\n\nThis is an outward-facing action (push + open a PR), so it gets the same explicit go-ahead as any\nother push or PR in this session, regardless of how directly `coco-ship` was invoked. State plainly:\n\n- Target repo and branch\n- Whether a guard bypass will be used, and the **exact** reason string (not a placeholder)\n- That this opens a PR against `main` — it does not push to `main` directly\n\nWait for a clear yes before Step 5. Invoking this skill is not itself that approval.\n\n### Step 5: Push\n\n```bash\ngit push -u origin \u003Cbranch>\n```\n\nOnly when Step 3 determined a bypass is needed:\n\n```bash\nGIT_GUARD_REASON=\"\u003Cspecific, real reason>\" git push -u origin \u003Cbranch>\n```\n\n**Never** `--no-verify`. **Never** a plain `--force`. A `--force-with-lease` update to an\nalready-open PR's branch is allowed, but still gets its own confirmation, separate from Step 4's.\n\n### Step 6: Open the PR\n\n```bash\ngh pr create --base main --head \u003Cbranch> --title \"\u003Ctitle>\" --body \"$(cat \u003C\u003C'EOF'\n## Summary\n\u003C2-3 bullets of what changed and why>\n\n## Test plan\n\u003Cwhat was verified, or a checklist of what to verify>\nEOF\n)\"\n```\n\nKeep the title under 70 characters. Put detail in the body, not the title.\n\n### Step 7: Wait for CI\n\n```bash\ngh pr checks \u003Cn> --watch\n```\n\nDon't report done while checks are still pending. If a check fails, say so plainly with the failure,\ndon't retry blindly.\n\n### Step 8: Report\n\nState the PR URL, the CI result, and the mergeable\u002Freview-required status. Say plainly that merging is\nthe user's call — **this skill never merges and never self-approves.** If the PR author can't\nself-approve (most repos), say that explicitly rather than implying the PR is ready to merge on its\nown.\n\n## Quick Reference\n\n| Step | Action | Confirmation needed? |\n|------|--------|----------------------|\n| 1 | Preflight (refuse on main) | — |\n| 2 | Commit | — |\n| 3 | Detect guard need | — |\n| 4 | State plan, ask | **Yes — always** |\n| 5 | Push | (covered by Step 4) |\n| 6 | Open PR | (covered by Step 4) |\n| 7 | Wait for CI | — |\n| 8 | Report | — |\n\n## Common Mistakes\n\n**Assuming the guard bypass is needed without checking**\n- **Problem:** Sets `GIT_GUARD_REASON` on every push, even to private or allowlisted repos, or misses\n  that the guard isn't even installed on this machine.\n- **Fix:** Always run Step 3's checks; only set the env var when the repo is genuinely public and\n  non-allowlisted.\n\n**Treating skill invocation as approval**\n- **Problem:** Runs Steps 5–6 immediately because the user said \"ship this,\" without a distinct\n  confirmation of the actual push\u002FPR plan.\n- **Fix:** Step 4 is a separate, explicit ask every time — state the repo, branch, guard reason (if\n  any), and that a PR (not a direct push to main) will follow.\n\n**Reporting success before CI resolves**\n- **Problem:** Says \"done\" right after `gh pr create`, while checks are still `pending`.\n- **Fix:** Step 7 watches until every check resolves, then Step 8 reports the real result.\n\n## Red Flags\n\n**Never:**\n- Push to `main` or `master` directly, no matter how it's requested\n- Use `--no-verify` or a plain `--force`\n- Auto-merge or self-approve a PR\n- Fabricate a `GIT_GUARD_REASON` instead of a specific, true one\n- Skip Step 4's confirmation because the work \"seems done\"\n\n**Always:**\n- Refuse and redirect if invoked while on `main`\u002F`master`\n- Check whether the guard bypass is actually needed rather than assuming\n- Get explicit confirmation before the push\u002FPR step\n- Wait for and report real CI status, not an assumed one\n\n## Integration\n\n**Formalizes:** Option 2 of `finishing-a-development-branch` (\"Push and Create PR\"), specialized for\nrepos carrying the corporate git-guard.\n\n**Distinct from:** `commands\u002Fteam\u002Fship.md` (`\u002Fteam:ship`, a full idea-to-product pipeline) and\n`systems\u002Fgsd\u002Fskills\u002Fgsd-ship` (GSD milestone-scoped). Neither overlaps with this skill's narrower job\n— shipping already-finished work through the guard and into a PR.\n\n**Pairs with:** `using-git-worktrees` for cleanup after the PR merges (not handled by this skill).\n","# Shipping to a CoCo-managed Repo\n\n## Overview\n\nFormalizes the branch → commit → guard-aware push → PR → CI-wait → report flow used for shipping\nwork to `coco-research\u002Fcoco` (or any repo carrying the same corporate git-guard pre-push hook), so it\ndoesn't have to be re-derived by hand each time.\n\n**Core principle:** Verify state → commit → detect whether the guard actually applies → confirm →\npush → open PR → wait for real CI → report. Never merge. Never push to `main` directly, regardless of\nhow it's asked.\n\n**Announce at start:** \"I'm using the coco-ship skill to ship this branch.\"\n\nThis is the direct formalization of Option 2 (\"Push and Create PR\") in\n`finishing-a-development-branch`, specialized for repos that carry the corporate git-guard. It\nassumes implementation is already done and reviewed — it doesn't replace planning skills like\n`brainstorming`, `writing-plans`, or GSD's phase workflow, and it doesn't run tests itself (that's\n`finishing-a-development-branch`'s Step 1, or the project's own CI).\n\n## The Process\n\n### Step 1: Preflight\n\n```bash\ngit status -sb\ngit branch --show-current\n```\n\n**If the current branch is `main` or `master`:** stop. Do not commit or push here. Offer to create a\nfeature branch first:\n\n```bash\ngit checkout -b \u003Cfeature-branch-name>\n```\n\n**If there's nothing to commit and the branch isn't already ahead of its upstream:** stop and say so\n— there's nothing to ship.\n\n### Step 2: Commit\n\nUse the standard git-commit protocol already in effect for this harness — this isn't a new\ninvention, just invoked from inside the skill:\n\n1. In parallel: `git status`, `git diff` (staged + unstaged), `git log` (recent messages, for style).\n2. Draft a commit message from the actual diff — why, not just what — matching the repo's existing\n   style.\n3. Stage named files explicitly. Never `git add -A` or `git add .`.\n4. Commit with a `Co-Authored-By` trailer, via a heredoc so formatting survives.\n5. `git status` again to confirm a clean tree.\n\nIf a pre-commit hook fails, fix the issue, re-stage, and create a **new** commit — never `--amend` a\ncommit that a failed hook means never actually landed.\n\n### Step 3: Detect whether the guard bypass is actually needed\n\nDon't assume — check:\n\n```bash\ngit remote -v\ngh repo view \u003Cowner>\u002F\u003Crepo> --json visibility,owner -q '\"\\(.visibility) \\(.owner.login)\"'\ngit config --show-origin --get core.hooksPath\n```\n\nA `GIT_GUARD_REASON` bypass is only needed when the repo is `PUBLIC` **and** the owner isn't on the\nguard's allowlist — check the actual guard config or ask the user which org(s) it allows, rather than\nassuming. If `core.hooksPath` doesn't point at the guard, don't assume a bypass is relevant on this\nmachine at all — say so.\n\n### Step 4: Confirm — every time, no exceptions\n\nThis is an outward-facing action (push + open a PR), so it gets the same explicit go-ahead as any\nother push or PR in this session, regardless of how directly `coco-ship` was invoked. State plainly:\n\n- Target repo and branch\n- Whether a guard bypass will be used, and the **exact** reason string (not a placeholder)\n- That this opens a PR against `main` — it does not push to `main` directly\n\nWait for a clear yes before Step 5. Invoking this skill is not itself that approval.\n\n### Step 5: Push\n\n```bash\ngit push -u origin \u003Cbranch>\n```\n\nOnly when Step 3 determined a bypass is needed:\n\n```bash\nGIT_GUARD_REASON=\"\u003Cspecific, real reason>\" git push -u origin \u003Cbranch>\n```\n\n**Never** `--no-verify`. **Never** a plain `--force`. A `--force-with-lease` update to an\nalready-open PR's branch is allowed, but still gets its own confirmation, separate from Step 4's.\n\n### Step 6: Open the PR\n\n```bash\ngh pr create --base main --head \u003Cbranch> --title \"\u003Ctitle>\" --body \"$(cat \u003C\u003C'EOF'\n## Summary\n\u003C2-3 bullets of what changed and why>\n\n## Test plan\n\u003Cwhat was verified, or a checklist of what to verify>\nEOF\n)\"\n```\n\nKeep the title under 70 characters. Put detail in the body, not the title.\n\n### Step 7: Wait for CI\n\n```bash\ngh pr checks \u003Cn> --watch\n```\n\nDon't report done while checks are still pending. If a check fails, say so plainly with the failure,\ndon't retry blindly.\n\n### Step 8: Report\n\nState the PR URL, the CI result, and the mergeable\u002Freview-required status. Say plainly that merging is\nthe user's call — **this skill never merges and never self-approves.** If the PR author can't\nself-approve (most repos), say that explicitly rather than implying the PR is ready to merge on its\nown.\n\n## Quick Reference\n\n| Step | Action | Confirmation needed? |\n|------|--------|----------------------|\n| 1 | Preflight (refuse on main) | — |\n| 2 | Commit | — |\n| 3 | Detect guard need | — |\n| 4 | State plan, ask | **Yes — always** |\n| 5 | Push | (covered by Step 4) |\n| 6 | Open PR | (covered by Step 4) |\n| 7 | Wait for CI | — |\n| 8 | Report | — |\n\n## Common Mistakes\n\n**Assuming the guard bypass is needed without checking**\n- **Problem:** Sets `GIT_GUARD_REASON` on every push, even to private or allowlisted repos, or misses\n  that the guard isn't even installed on this machine.\n- **Fix:** Always run Step 3's checks; only set the env var when the repo is genuinely public and\n  non-allowlisted.\n\n**Treating skill invocation as approval**\n- **Problem:** Runs Steps 5–6 immediately because the user said \"ship this,\" without a distinct\n  confirmation of the actual push\u002FPR plan.\n- **Fix:** Step 4 is a separate, explicit ask every time — state the repo, branch, guard reason (if\n  any), and that a PR (not a direct push to main) will follow.\n\n**Reporting success before CI resolves**\n- **Problem:** Says \"done\" right after `gh pr create`, while checks are still `pending`.\n- **Fix:** Step 7 watches until every check resolves, then Step 8 reports the real result.\n\n## Red Flags\n\n**Never:**\n- Push to `main` or `master` directly, no matter how it's requested\n- Use `--no-verify` or a plain `--force`\n- Auto-merge or self-approve a PR\n- Fabricate a `GIT_GUARD_REASON` instead of a specific, true one\n- Skip Step 4's confirmation because the work \"seems done\"\n\n**Always:**\n- Refuse and redirect if invoked while on `main`\u002F`master`\n- Check whether the guard bypass is actually needed rather than assuming\n- Get explicit confirmation before the push\u002FPR step\n- Wait for and report real CI status, not an assumed one\n\n## Integration\n\n**Formalizes:** Option 2 of `finishing-a-development-branch` (\"Push and Create PR\"), specialized for\nrepos carrying the corporate git-guard.\n\n**Distinct from:** `commands\u002Fteam\u002Fship.md` (`\u002Fteam:ship`, a full idea-to-product pipeline) and\n`systems\u002Fgsd\u002Fskills\u002Fgsd-ship` (GSD milestone-scoped). Neither overlaps with this skill's narrower job\n— shipping already-finished work through the guard and into a PR.\n\n**Pairs with:** `using-git-worktrees` for cleanup after the PR merges (not handled by this skill).\n",{"name":5,"domain":49,"description":7,"user-invocable":50},"engineering",true,"cd89f013b617f7eea982a9bbc60e992974fda2aa","skills\u002Fcoco-ship",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":50},[62,65,68],{"tool":63,"command":64},"npx","npx skills add coco-research\u002Fcoco --skill coco-ship",{"tool":66,"command":67},"bunx","bunx skills add coco-research\u002Fcoco --skill coco-ship",{"tool":69,"command":70},"pnpm","pnpm dlx skills add coco-research\u002Fcoco --skill coco-ship","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Fcoco-ship\u002FSKILL.md",[],[74,99,109,127,162,181],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":81,"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",[80],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"super","trading super intelligence","intelligence","trading","validator","personas","local","composites","studio","team","across","world","first","gated","2026","lm studio","local-first",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"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",[105],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[107,82,108,84,86,87,88,89,90,91,92,93,94,95,96,97,98],"strategy","strategy super intelligence",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":121,"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",[115,116],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[122,82,123,124,125,84,86,87,88,89,126,90,91,92,93,94,95,96,97,98],"risk","risk compliance super intelligence","compliance","risk compliance","grc",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":146,"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",[133,136,139,140,143],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":141,"categoryName":142,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":144,"categoryName":145,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000032","设计师",[147,148,84,149,82,150,151,152,153,154,155,91,92,156,157,96,158,159,160,161],"design","product","product design","product design super intelligence","foundations","product-design","decision","design systems","usability","leadership","ux","brain","craft","metrics","trust",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":170,"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",[168,169],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},[171,82,172,84,173,174,161,175,87,176,177,178,107,91,92,179,124,180,96,158],"ip","legal ip super intelligence","legal","sep","tech","litigation","ai governance","open","open-source","governance",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"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",[187],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[189,82,190,191,84,174,161,192,193,87,194,195,107,91,92,196,197,198,199,96],"healthcare","healthcare life sciences super intelligence","life","economics","discovery","policy","clinical","clinical trials","health","trials","genomics"]