[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HTQJDKWKQ07EZT0VR7JRH":3,"skill-same:01M71HTQJDKWKQ07EZT0VR7JRH":100},{"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":40,"publishedAt":61,"linkOnly":62,"markdownContent":63,"markdownBody":64,"frontMatter":65,"refName":78,"commitSha":79,"skillDirectory":80,"forksCount":14,"repositoryHtmlUrl":81,"repositoryHomepageUrl":6,"ownerHtmlUrl":82,"ownerBlogUrl":83,"ownerDescription":84,"updatedAt":85,"install":86,"resources":99},"01M71HTQJDKWKQ07EZT0VR7JRH","research-ops-skills",null,"Use when planning, funding, scoping, or synthesizing enterprise research across workstreams — clinical study design, R&D program finance, market sizing\u002Fsurveys, or product\u002Fuser research. Triggers on \"design this clinical study\", \"what sample size\", \"R&D budget\", \"burn rate\", \"capitalize or expense\", \"TAM SAM SOM\", \"market sizing\", \"survey design\", \"segment the market\", \"plan user interviews\", \"usability test\", \"synthesize research insights\". Forks context to route to one of four Research-Operations sub-skills (clinical-research, research-finance, market-research, product-research) and returns a digest. Distinct from ra-qm-team (regulatory submission), finance (corporate close\u002Fvaluation), research\u002Fgrants (funding discovery), product-team (persona\u002Fjourney\u002Flive experiments), and marketing-skill (campaign analytics).","agency-black\u002FSkills","agency-black","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234862658?v=4","01M6HWVFPNGNR5N2CX9ECSAD57","agencia.black","01M719WF77BF3HN0N9FK1APEFY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fresearch-ops\u002Fskills\u002Fresearch-ops-skills\u002FSKILL.md",[18,23,26,29,34,37],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000035","市场营销",{"categoryNo":38,"categoryName":39,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000040","财务",[41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60],"research","research ops skills","ops","research ops","close","design","synthesize research","synthesize","survey design","campaign","rd","research-finance","usability","product-research","survey","market-research","clinical-research","research-ops","plan","team","2026-11-10 10:12:30",false,"---\nname: research-ops-skills\ndescription: Use when planning, funding, scoping, or synthesizing enterprise research across workstreams — clinical study design, R&D program finance, market sizing\u002Fsurveys, or product\u002Fuser research. Triggers on \"design this clinical study\", \"what sample size\", \"R&D budget\", \"burn rate\", \"capitalize or expense\", \"TAM SAM SOM\", \"market sizing\", \"survey design\", \"segment the market\", \"plan user interviews\", \"usability test\", \"synthesize research insights\". Forks context to route to one of four Research-Operations sub-skills (clinical-research, research-finance, market-research, product-research) and returns a digest. Distinct from ra-qm-team (regulatory submission), finance (corporate close\u002Fvaluation), research\u002Fgrants (funding discovery), product-team (persona\u002Fjourney\u002Flive experiments), and marketing-skill (campaign analytics).\ncontext: fork\nversion: 2.9.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [research-ops, clinical-research, research-finance, market-research, product-research, rd, orchestrator]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Research Operations — Domain Orchestrator\n\nThe Research Operations surface is **how the enterprise plans, funds, scopes, and synthesizes research** across four workstreams: clinical R&D, R&D finance, market research, and product research. This orchestrator forks its context, routes your inquiry to one of four sub-skills, then returns a digest. Heavy intake (protocol drafts, program ledgers, survey exports, interview transcripts) stays in the forked context.\n\nThis is the enterprise counterpart to the academic `research\u002F` domain. If your question is about **finding** literature, grants, or patents, use `research\u002F`. If it is about **planning, funding, scoping, or synthesizing** research as an operational discipline, you are in the right place.\n\n## When to invoke\n\n| Symptom | Sub-skill |\n|---|---|\n| \"We're designing a Phase 2 trial — what's the endpoint and sample size?\" | `clinical-research` |\n| \"What's our R&D program burn, and is this cost CapEx or OpEx?\" | `research-finance` |\n| \"What's the TAM for this product, and how do we survey the segment?\" | `market-research` |\n| \"How many users do we interview, and how do we synthesize the findings?\" | `product-research` |\n\n## Routing logic (deterministic)\n\nSame two-signal threshold pattern as `commercial-skills`. Single-signal → clarifying question. Mixed signals → highest-confidence first, chain second in a follow-up turn. Never silently chain.\n\n### Signal table\n\n| Signal class | Keywords | Sub-skill |\n|---|---|---|\n| **CLINICAL** | clinical trial, study design, protocol, endpoint, sample size, power, phase 1\u002F2\u002F3, biostatistics, eligibility, feasibility, estimand | `clinical-research` |\n| **RD_FINANCE** | R&D budget, program budget, burn, runway, F&A, indirect rate, overhead, capitalize vs expense, R&D capex, portfolio ROI, rNPV | `research-finance` |\n| **MARKET** | TAM, SAM, SOM, market sizing, survey design, sampling, margin of error, segmentation, competitive intelligence, market research | `market-research` |\n| **PRODUCT** | user interview, JTBD, usability test, concept test, prototype test, discovery research, research repository, insight synthesis, saturation | `product-research` |\n\n## Workflow (Matt Pocock grill discipline)\n\nDerived from Matt Pocock's `grill-with-docs` pattern: **explore-then-ask, one question per turn with a recommended answer, walk the decision tree depth-first, track dependencies, anchor every challenge in the research canon** (`references\u002F` of each sub-skill).\n\n### Step 1 — Explore before asking\n\nCheck the user's working directory first:\n- Is there a protocol draft, program ledger, TAM model, or interview guide already in the workspace?\n- Does the inquiry already disambiguate the lane (e.g., \"what sample size for a two-arm trial\" — that's `clinical-research`, no question needed)?\n- Is there an artifact filename that resolves the lane (`protocol.json` → clinical; `program-budget.json` → finance; `tam-model.json` → market; `interview-guide.md` → product)?\n\nIf the workspace resolves the lane, **route silently**.\n\n### Step 2 — If still ambiguous, ONE forcing question with a recommended answer\n\nMatt's rule: never bundle. Always recommend.\n\nPattern:\n```\nQ1\u002F1: [precise question naming the two candidate lanes]\nRecommended: [Lane X, because \u003Csignal-table rationale>]\n\n(Confirm, or override?)\n```\n\n### Step 3 — Decision-tree walk for multi-lane inquiries\n\nIf the inquiry legitimately crosses two lanes (e.g., \"design this trial AND budget it\" = CLINICAL + RD_FINANCE), walk depth-first:\n\n1. Highest-confidence lane first → run sub-skill in forked context → digest\n2. Ask: \"Now run [second lane]? Recommended: yes, because [dependency].\"\n3. Confirm before chaining.\n\nNever silently chain.\n\n### Step 4 — Invoke sub-skill in forked context\n\nForward original prompt + structured inputs (protocol JSON, program ledger CSV, market model, observation export).\n\n### Step 5 — Return digest with cited canon challenge\n\n≤ 200 words: analyzed, top 3 findings (anchored to a canon citation), top 3 next actions (named human owner where applicable), artifact path, and **one grill challenge** for the user. Examples:\n\n- \"Your power calc assumes a 0.5 effect size with no published anchor. ICH E9 requires a justified, clinically meaningful difference. Where did 0.5 come from?\"\n- \"Your TAM is a single top-down number (1% of a $40B market). Bessemer market-sizing discipline requires a bottoms-up cross-check. What's units × price × adoption?\"\n\n## Forcing-question library (grill-with-docs pattern)\n\nGrill the user on lane-defining decisions before invoking the sub-skill. One per turn, recommended answer, canon citation:\n\n- **CLINICAL lane**: \"Is your primary endpoint a clinical outcome or a surrogate — and if surrogate, is it validated for this indication? Recommended: clinical outcome unless the surrogate is on FDA's validated table. Canon: FDA Surrogate Endpoint Table; BEST glossary.\"\n- **RD_FINANCE lane**: \"Is this spend in the research phase or the development phase, and can you evidence technical feasibility? Recommended: research = expense; development = capitalize-candidate only with feasibility evidence, routed to a named finance owner. Canon: IAS 38; ASC 730.\"\n- **MARKET lane**: \"Is your TAM top-down or bottoms-up — and have you computed it both ways to triangulate? Recommended: both; reconcile the delta. Canon: Bessemer \u002F a16z market-sizing; Fermi estimation.\"\n- **PRODUCT lane**: \"Is this study generative (discover problems) or evaluative (test a solution)? Recommended: name it first; the method follows. Canon: Rohrer's landscape of UX research methods (NN\u002Fg).\"\n\nNever run a sub-skill until the lane-defining decision is locked.\n\n## Onboarding-first (per sub-skill)\n\nBefore invoking a sub-skill for the first time in a workspace, point the user at that skill's onboarding questionnaire so the tools run pre-configured to their context:\n\n```bash\npython3 skills\u002F\u003Csub-skill>\u002Fscripts\u002Fonboard.py          # interactive Q&A\npython3 skills\u002F\u003Csub-skill>\u002Fscripts\u002Fonboard.py --show    # questions + current config\n```\n\nEach sub-skill has its **own** question set (clinical: area\u002Falpha\u002Fpower\u002Fdropout\u002Fowners · finance: area\u002FF&A\u002Frunway\u002Fstandard\u002Fowner · market: profile\u002Fconfidence\u002FMoE\u002Fmethod · product: profile\u002Finsight-threshold\u002Fmethod\u002Fstakes). Answers persist to `~\u002F.config\u002Fresearch-ops\u002F\u003Csub-skill>.json` (or `.\u002F.research-ops\u002F\u003Csub-skill>.json` with `--scope project`) and are consumed automatically by every tool in that skill. Customization is mandatory discipline here, not decoration — surface the onboarding step when a user starts a fresh research workstream.\n\n## Autoresearch handoff (isolated, opt-in)\n\nEach sub-skill ships its own `scripts\u002Far_evaluator.py` — an **isolated** bridge to `engineering\u002Fautoresearch-agent`. Invoke autoresearch **only when the user explicitly asks** to \"optimize\", \"improve\", or \"run a loop\". The handoff is per-skill (no shared coupling): the loop edits the skill's input file and the evaluator scores it (clinical → `feasibility_composite` higher; finance → `runway_months` higher; market → `tam_divergence` lower; product → `validated_insights` higher). Never auto-start a loop; never let the loop edit the evaluator.\n\n## Assumptions\n\n1. User has research authority OR is preparing analysis for someone who does.\n2. User wants **deterministic decision support**, not the final answer — a clinician approves the protocol, a controller books the entry, the human picks the market number.\n3. Inputs may be partial — every sub-skill ships a templated sample so the user can see the shape before filling in their own.\n\n## Non-goals\n\n- Not an EDC, clinical-trial-management system, accounting system, survey platform, or research repository.\n- Does not give clinical, accounting, or legal advice as fact. Every output is **a recommendation + named human owner**.\n- Does not store research history across sessions.\n\n## Distinct from\n\n- **`research\u002F` (academic)** — that domain **finds** literature, grants, and patents. This domain **plans, funds, scopes, and synthesizes** research.\n- **`ra-qm-team`** — that's **regulatory\u002FQM submission** (ISO 13485\u002F14971, MDR, FDA 510(k)\u002FPMA\u002FQSR). clinical-research designs the **study**; it routes submission out to ra-qm-team.\n- **`finance\u002Ffinancial-analysis`** — that's **corporate close + valuation**. research-finance manages **R&D program\u002Fportfolio spend**.\n- **`research\u002Fgrants`** — that's **funding discovery**. research-finance manages **money already won**.\n- **`product-team`** — that's **persona\u002Fjourney artifacts, discovery sprints, and live A\u002FB experiments**. product-research is the **method + repository discipline**.\n- **`marketing-skill`** — that's **campaign analytics and demand-gen**. market-research is **upstream methodology**.\n\n## Output artifacts\n\n| Sub-skill | Artifact |\n|---|---|\n| clinical-research | `protocol_synopsis.md` + `sample_size.json` |\n| research-finance | `rd_program_budget.md` + `capex_opex_routing.json` |\n| market-research | `market_sizing.md` + `sample_plan.json` |\n| product-research | `research_plan.md` + `insight_synthesis.json` |\n\n## Anti-patterns (do not)\n\n- ❌ Present a clinical power\u002Fendpoint output as fact — it is an **estimate** with a named clinical owner\n- ❌ Auto-decide capitalize-vs-expense — route to a **named finance owner**\n- ❌ Report a market size as a single unsourced number — show **method + both-ways triangulation + assumptions**\n- ❌ Assert a product insight from a single participant — flag it as an **anecdote**\n- ❌ Run all 4 sub-skills \"to be thorough\" — pick one, digest, chain if needed\n\n## References\n\n- Clinical canon: ICH E8(R1)\u002FE9\u002FE9(R1), CONSORT, SPIRIT, FDA Multiple Endpoints\n- R&D finance canon: IAS 38, ASC 730, 2 CFR 200, Cooper stage-gate\n- Market canon: Cochran, Dillman, Kotler, Bessemer market-sizing\n- Product canon: Nielsen, Guest et al., Christensen JTBD, ResearchOps\u002FPolaris\n- Path-B build pattern: `documentation\u002Fimplementation\u002Fresearch-ops-expansion-plan.md`\n","# Research Operations — Domain Orchestrator\n\nThe Research Operations surface is **how the enterprise plans, funds, scopes, and synthesizes research** across four workstreams: clinical R&D, R&D finance, market research, and product research. This orchestrator forks its context, routes your inquiry to one of four sub-skills, then returns a digest. Heavy intake (protocol drafts, program ledgers, survey exports, interview transcripts) stays in the forked context.\n\nThis is the enterprise counterpart to the academic `research\u002F` domain. If your question is about **finding** literature, grants, or patents, use `research\u002F`. If it is about **planning, funding, scoping, or synthesizing** research as an operational discipline, you are in the right place.\n\n## When to invoke\n\n| Symptom | Sub-skill |\n|---|---|\n| \"We're designing a Phase 2 trial — what's the endpoint and sample size?\" | `clinical-research` |\n| \"What's our R&D program burn, and is this cost CapEx or OpEx?\" | `research-finance` |\n| \"What's the TAM for this product, and how do we survey the segment?\" | `market-research` |\n| \"How many users do we interview, and how do we synthesize the findings?\" | `product-research` |\n\n## Routing logic (deterministic)\n\nSame two-signal threshold pattern as `commercial-skills`. Single-signal → clarifying question. Mixed signals → highest-confidence first, chain second in a follow-up turn. Never silently chain.\n\n### Signal table\n\n| Signal class | Keywords | Sub-skill |\n|---|---|---|\n| **CLINICAL** | clinical trial, study design, protocol, endpoint, sample size, power, phase 1\u002F2\u002F3, biostatistics, eligibility, feasibility, estimand | `clinical-research` |\n| **RD_FINANCE** | R&D budget, program budget, burn, runway, F&A, indirect rate, overhead, capitalize vs expense, R&D capex, portfolio ROI, rNPV | `research-finance` |\n| **MARKET** | TAM, SAM, SOM, market sizing, survey design, sampling, margin of error, segmentation, competitive intelligence, market research | `market-research` |\n| **PRODUCT** | user interview, JTBD, usability test, concept test, prototype test, discovery research, research repository, insight synthesis, saturation | `product-research` |\n\n## Workflow (Matt Pocock grill discipline)\n\nDerived from Matt Pocock's `grill-with-docs` pattern: **explore-then-ask, one question per turn with a recommended answer, walk the decision tree depth-first, track dependencies, anchor every challenge in the research canon** (`references\u002F` of each sub-skill).\n\n### Step 1 — Explore before asking\n\nCheck the user's working directory first:\n- Is there a protocol draft, program ledger, TAM model, or interview guide already in the workspace?\n- Does the inquiry already disambiguate the lane (e.g., \"what sample size for a two-arm trial\" — that's `clinical-research`, no question needed)?\n- Is there an artifact filename that resolves the lane (`protocol.json` → clinical; `program-budget.json` → finance; `tam-model.json` → market; `interview-guide.md` → product)?\n\nIf the workspace resolves the lane, **route silently**.\n\n### Step 2 — If still ambiguous, ONE forcing question with a recommended answer\n\nMatt's rule: never bundle. Always recommend.\n\nPattern:\n```\nQ1\u002F1: [precise question naming the two candidate lanes]\nRecommended: [Lane X, because \u003Csignal-table rationale>]\n\n(Confirm, or override?)\n```\n\n### Step 3 — Decision-tree walk for multi-lane inquiries\n\nIf the inquiry legitimately crosses two lanes (e.g., \"design this trial AND budget it\" = CLINICAL + RD_FINANCE), walk depth-first:\n\n1. Highest-confidence lane first → run sub-skill in forked context → digest\n2. Ask: \"Now run [second lane]? Recommended: yes, because [dependency].\"\n3. Confirm before chaining.\n\nNever silently chain.\n\n### Step 4 — Invoke sub-skill in forked context\n\nForward original prompt + structured inputs (protocol JSON, program ledger CSV, market model, observation export).\n\n### Step 5 — Return digest with cited canon challenge\n\n≤ 200 words: analyzed, top 3 findings (anchored to a canon citation), top 3 next actions (named human owner where applicable), artifact path, and **one grill challenge** for the user. Examples:\n\n- \"Your power calc assumes a 0.5 effect size with no published anchor. ICH E9 requires a justified, clinically meaningful difference. Where did 0.5 come from?\"\n- \"Your TAM is a single top-down number (1% of a $40B market). Bessemer market-sizing discipline requires a bottoms-up cross-check. What's units × price × adoption?\"\n\n## Forcing-question library (grill-with-docs pattern)\n\nGrill the user on lane-defining decisions before invoking the sub-skill. One per turn, recommended answer, canon citation:\n\n- **CLINICAL lane**: \"Is your primary endpoint a clinical outcome or a surrogate — and if surrogate, is it validated for this indication? Recommended: clinical outcome unless the surrogate is on FDA's validated table. Canon: FDA Surrogate Endpoint Table; BEST glossary.\"\n- **RD_FINANCE lane**: \"Is this spend in the research phase or the development phase, and can you evidence technical feasibility? Recommended: research = expense; development = capitalize-candidate only with feasibility evidence, routed to a named finance owner. Canon: IAS 38; ASC 730.\"\n- **MARKET lane**: \"Is your TAM top-down or bottoms-up — and have you computed it both ways to triangulate? Recommended: both; reconcile the delta. Canon: Bessemer \u002F a16z market-sizing; Fermi estimation.\"\n- **PRODUCT lane**: \"Is this study generative (discover problems) or evaluative (test a solution)? Recommended: name it first; the method follows. Canon: Rohrer's landscape of UX research methods (NN\u002Fg).\"\n\nNever run a sub-skill until the lane-defining decision is locked.\n\n## Onboarding-first (per sub-skill)\n\nBefore invoking a sub-skill for the first time in a workspace, point the user at that skill's onboarding questionnaire so the tools run pre-configured to their context:\n\n```bash\npython3 skills\u002F\u003Csub-skill>\u002Fscripts\u002Fonboard.py          # interactive Q&A\npython3 skills\u002F\u003Csub-skill>\u002Fscripts\u002Fonboard.py --show    # questions + current config\n```\n\nEach sub-skill has its **own** question set (clinical: area\u002Falpha\u002Fpower\u002Fdropout\u002Fowners · finance: area\u002FF&A\u002Frunway\u002Fstandard\u002Fowner · market: profile\u002Fconfidence\u002FMoE\u002Fmethod · product: profile\u002Finsight-threshold\u002Fmethod\u002Fstakes). Answers persist to `~\u002F.config\u002Fresearch-ops\u002F\u003Csub-skill>.json` (or `.\u002F.research-ops\u002F\u003Csub-skill>.json` with `--scope project`) and are consumed automatically by every tool in that skill. Customization is mandatory discipline here, not decoration — surface the onboarding step when a user starts a fresh research workstream.\n\n## Autoresearch handoff (isolated, opt-in)\n\nEach sub-skill ships its own `scripts\u002Far_evaluator.py` — an **isolated** bridge to `engineering\u002Fautoresearch-agent`. Invoke autoresearch **only when the user explicitly asks** to \"optimize\", \"improve\", or \"run a loop\". The handoff is per-skill (no shared coupling): the loop edits the skill's input file and the evaluator scores it (clinical → `feasibility_composite` higher; finance → `runway_months` higher; market → `tam_divergence` lower; product → `validated_insights` higher). Never auto-start a loop; never let the loop edit the evaluator.\n\n## Assumptions\n\n1. User has research authority OR is preparing analysis for someone who does.\n2. User wants **deterministic decision support**, not the final answer — a clinician approves the protocol, a controller books the entry, the human picks the market number.\n3. Inputs may be partial — every sub-skill ships a templated sample so the user can see the shape before filling in their own.\n\n## Non-goals\n\n- Not an EDC, clinical-trial-management system, accounting system, survey platform, or research repository.\n- Does not give clinical, accounting, or legal advice as fact. Every output is **a recommendation + named human owner**.\n- Does not store research history across sessions.\n\n## Distinct from\n\n- **`research\u002F` (academic)** — that domain **finds** literature, grants, and patents. This domain **plans, funds, scopes, and synthesizes** research.\n- **`ra-qm-team`** — that's **regulatory\u002FQM submission** (ISO 13485\u002F14971, MDR, FDA 510(k)\u002FPMA\u002FQSR). clinical-research designs the **study**; it routes submission out to ra-qm-team.\n- **`finance\u002Ffinancial-analysis`** — that's **corporate close + valuation**. research-finance manages **R&D program\u002Fportfolio spend**.\n- **`research\u002Fgrants`** — that's **funding discovery**. research-finance manages **money already won**.\n- **`product-team`** — that's **persona\u002Fjourney artifacts, discovery sprints, and live A\u002FB experiments**. product-research is the **method + repository discipline**.\n- **`marketing-skill`** — that's **campaign analytics and demand-gen**. market-research is **upstream methodology**.\n\n## Output artifacts\n\n| Sub-skill | Artifact |\n|---|---|\n| clinical-research | `protocol_synopsis.md` + `sample_size.json` |\n| research-finance | `rd_program_budget.md` + `capex_opex_routing.json` |\n| market-research | `market_sizing.md` + `sample_plan.json` |\n| product-research | `research_plan.md` + `insight_synthesis.json` |\n\n## Anti-patterns (do not)\n\n- ❌ Present a clinical power\u002Fendpoint output as fact — it is an **estimate** with a named clinical owner\n- ❌ Auto-decide capitalize-vs-expense — route to a **named finance owner**\n- ❌ Report a market size as a single unsourced number — show **method + both-ways triangulation + assumptions**\n- ❌ Assert a product insight from a single participant — flag it as an **anecdote**\n- ❌ Run all 4 sub-skills \"to be thorough\" — pick one, digest, chain if needed\n\n## References\n\n- Clinical canon: ICH E8(R1)\u002FE9\u002FE9(R1), CONSORT, SPIRIT, FDA Multiple Endpoints\n- R&D finance canon: IAS 38, ASC 730, 2 CFR 200, Cooper stage-gate\n- Market canon: Cochran, Dillman, Kotler, Bessemer market-sizing\n- Product canon: Nielsen, Guest et al., Christensen JTBD, ResearchOps\u002FPolaris\n- Path-B build pattern: `documentation\u002Fimplementation\u002Fresearch-ops-expansion-plan.md`\n",{"name":5,"tags":66,"author":68,"context":69,"license":15,"version":70,"description":7,"compatible_tools":71},[58,57,52,56,54,51,67],"orchestrator","claude-code-skills","fork","2.9.0",[72,73,74,75,76,77],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","681496e0662f4c45c4758fae9d4510ae87311bf2","research-ops\u002Fskills\u002Fresearch-ops-skills","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills","https:\u002F\u002Fgithub.com\u002Fagency-black","http:\u002F\u002Fwww.dogma.black","Las grandes ideas merecen una ejecución impecable. Construimos plataformas web, aplicaciones y ecosistemas digitales completos. Esta Trinidad es nuestro dogma.","2026-05-29 16:13:55",{"source":8,"skillName":5,"commands":87,"prompt":97,"zipAvailable":98},[88,91,94],{"tool":89,"command":90},"npx","npx skills add agency-black\u002FSkills --skill research-ops-skills",{"tool":92,"command":93},"bunx","bunx skills add agency-black\u002FSkills --skill research-ops-skills",{"tool":95,"command":96},"pnpm","pnpm dlx skills add agency-black\u002FSkills --skill research-ops-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fresearch-ops\u002Fskills\u002Fresearch-ops-skills\u002FSKILL.md",true,[],[101,128,153,183,208,233],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":61},"01M71JZVZ0TVW7Z5DQBRWSBG8A","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fzarr-python\u002FSKILL.md",[],[108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"zarr python","python","zarr","arrays","Cloud Storage","remote","workflows","scientific","read","write","edit","parallel","dask","for","s3fs","use","numpy","s3","scientific computing","scale",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":61},"01M71JYXC5VAEJT8KXN5GRK32S","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FSKILL.md",[135],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[137,138,41,139,140,141,142,109,143,114,144,145,146,147,148,149,150,151,74,152],"xvary","stock","xvary stock research","sec edgar","community","equity","thesis","analysis","code","Market","compare","market data","analyze","with","codex","2026",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":157,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":167,"publishedAt":61},"01M71JVSDPDQ5040YBN6J1ASKY","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[168,169,170,121,171,172,173,174,175,176,177,150,178,179,180,181,182],"webapp","testing","webapp testing","applications","local","frontend","debugging","toolkit","logs","browser","playwright","web","behavior","ui","screenshots",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":157,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":191,"publishedAt":61},"01M71JV64CW7R6FYYK9JWWGW0X","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[190],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},[192,193,194,179,195,196,197,121,198,199,173,200,123,201,202,203,204,205,206,207],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","components","react","multi","state","routing","state management",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":61},"01M71JS4X2FRY41DE84DEP06MN","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-view-transitions\u002FSKILL.md",[214],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},[203,216,217,218,219,220,221,222,223,197,224,225,226,227,228,202,229,230,231,232],"vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","types","states","element","implementing","when","api","route","create","libraries",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":240,"publishedAt":61},"01M71JS1WZ1J4F9YVC2203JBJW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-native-skills\u002FSKILL.md",[239],{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},[219,241,203,242,243,244,245,246,247,121,248,227,249,123,250,251,228,252,253,202],"vercel react native skills","react native","native","react native skills","modules","platform","animations","performance","triggers","react native components","apps","best practices","tasks"]