[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FK5C742Z8KFVCVE2MN4VS":3,"skill-same:01M79FK5C742Z8KFVCVE2MN4VS":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79FK5C742Z8KFVCVE2MN4VS","research-router-skill",null,"Route broad or ambiguous life-sciences research requests to the right skills, normalize core entities, optionally parallelize independent evidence gathering with subagents when available, and synthesize a concise evidence-backed answer. Use when a user asks a general life-sciences question that could span multiple sources or analysis types.","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch-router-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: research-router-skill\ndescription: Route broad or ambiguous life-sciences research requests to the right skills, normalize core entities, optionally parallelize independent evidence gathering with subagents when available, and synthesize a concise evidence-backed answer. Use when a user asks a general life-sciences question that could span multiple sources or analysis types.\n---\n\n## Research Router\n\nUse this skill as the default orchestration layer for broad life-sciences research requests.\n\nDo not use it for narrow single-source lookups when a more specific skill already matches the request cleanly.\n\n## Primary Responsibility\n\nTurn an open-ended research question into a small, defensible retrieval plan:\n\n1. understand the research objective\n2. normalize the main entities\n3. select the minimum useful set of downstream skills\n4. gather evidence\n5. synthesize the answer for the user\n\nThe router owns the framing and the final synthesis. It should not dump raw source payloads unless the user explicitly asks for them.\n\n## When To Use This Skill\n\nUse this skill when any of the following are true:\n\n- the user asks a broad question such as `what is known about ...`\n- the question could require more than one evidence type\n- the right source is unclear at the start\n- the request mixes entities, for example gene plus disease, variant plus phenotype, protein plus ligand, or pathway plus dataset\n- the user wants a synthesized answer rather than a single database lookup\n\n## Research Task Classification\n\nStart by classifying the request into one or more lanes:\n\n- human genetics and variant interpretation\n- locus-to-gene prioritization\n- expression, tissue, or cell-type context\n- pathway, network, or functional biology\n- protein structure and mechanism\n- chemistry, ligands, and pharmacology\n- clinical, translational, or cancer evidence\n- literature, preprints, and public dataset discovery\n- metabolomics, proteomics, or microbiome context\n\nPrefer 1 to 3 lanes. Only expand further if the user explicitly asks for a broad landscape review.\n\n## Entity Normalization\n\nNormalize the key entities before deep retrieval.\n\nCommon patterns:\n\n- gene or protein: `ncbi-clinicaltables-skill`, `ensembl-skill`, `uniprot-skill`\n- disease or phenotype: `efo-ontology-skill`, `opentargets-skill`\n- variant: `clinvar-variation-skill`, `ensembl-skill`, cohort-specific PheWAS skills\n- compound or metabolite: `chembl-skill`, `pubchem-pug-skill`, `chebi-skill`, `hmdb-skill`\n- pathway or function: `reactome-skill`, `quickgo-skill`, `string-skill`\n- accession or dataset identifier: `ncbi-datasets-skill`, `biostudies-arrayexpress-skill`, `pride-skill`, `metabolights-skill`\n\nDo not start broad evidence collection until the important entities are stable enough to route correctly.\n\n## Skill Selection Heuristics\n\nChoose the smallest set of skills that can answer the question well.\n\nExamples:\n\n- target or disease evidence review:\n  `opentargets-skill`, `gwas-catalog-skill`, `gtex-eqtl-skill`, `human-protein-atlas-skill`\n- variant interpretation:\n  `clinvar-variation-skill`, `gnomad-graphql-skill`, `ensembl-skill`, one or more cohort PheWAS skills\n- locus-to-gene mapping:\n  `locus-to-gene-mapper-skill`, or its component genetics skills when the user wants a custom workflow\n- structure and mechanism:\n  `alphafold-skill`, `rcsb-pdb-skill`, `uniprot-skill`, `reactome-skill`\n- chemistry and pharmacology:\n  `chembl-skill`, `bindingdb-skill`, `pubchem-pug-skill`, `pharmgkb-skill`\n- clinical and translational:\n  `clinicaltrials-skill`, `cbioportal-skill`, `civic-skill`\n- literature and dataset discovery:\n  `ncbi-entrez-skill`, `ncbi-pmc-skill`, `biorxiv-skill`, `biostudies-arrayexpress-skill`, `ncbi-datasets-skill`\n\nPrefer direct lookups before expensive multi-step chains.\n\n## Subagent And Parallelization Guidance\n\nIf Codex subagents are available, use them only when the work cleanly decomposes into independent lanes.\n\nGood candidates for subagents:\n\n- genetics, expression, structure, chemistry, and clinical evidence can be gathered independently for the same question\n- multiple loci, variants, genes, compounds, or datasets need parallel comparison\n- a broad landscape review requires separate evidence summaries before synthesis\n\nKeep these steps with the coordinating agent:\n\n- initial interpretation of the user request\n- entity normalization and final scope decisions\n- conflict resolution across evidence sources\n- final synthesis and recommendation writing\n\nAvoid subagents when:\n\n- one specific skill already answers the question\n- later steps depend tightly on earlier intermediate outputs\n- the work is mostly identifier resolution or narrow follow-up lookup\n- the extra coordination cost is likely to exceed the retrieval benefit\n\nWhen delegating, give each subagent a bounded read-only objective such as one evidence family or one comparison unit. Each subagent should return:\n\n- what it checked\n- the key findings\n- the main caveats\n- which skills or sources it used\n- any artifact paths it produced\n\nThe coordinating agent is responsible for reconciling overlaps, contradictions, and evidence gaps.\n\n## Output Contract\n\nReturn a concise answer structured around the user's question, not around the tools.\n\nUnless the user asks for a different format, include:\n\n1. direct answer or working conclusion\n2. key evidence by lane\n3. main caveats or unresolved questions\n4. recommended next analyses or follow-up lookups\n\nIf the task is exploratory, explicitly distinguish:\n\n- evidence that supports a conclusion\n- evidence that is only suggestive\n- evidence that is missing or contradictory\n\n## Operating Rules\n\n- prefer concise source-backed synthesis over large raw dumps\n- escalate to multi-skill workflows only when the question requires synthesis\n- state important cohort, ancestry, assay, tissue, and study-design limitations\n- do not overstate causality from association-only evidence\n- if a downstream skill can answer the request directly, hand off to it instead of keeping the router in the foreground\n","## Research Router\n\nUse this skill as the default orchestration layer for broad life-sciences research requests.\n\nDo not use it for narrow single-source lookups when a more specific skill already matches the request cleanly.\n\n## Primary Responsibility\n\nTurn an open-ended research question into a small, defensible retrieval plan:\n\n1. understand the research objective\n2. normalize the main entities\n3. select the minimum useful set of downstream skills\n4. gather evidence\n5. synthesize the answer for the user\n\nThe router owns the framing and the final synthesis. It should not dump raw source payloads unless the user explicitly asks for them.\n\n## When To Use This Skill\n\nUse this skill when any of the following are true:\n\n- the user asks a broad question such as `what is known about ...`\n- the question could require more than one evidence type\n- the right source is unclear at the start\n- the request mixes entities, for example gene plus disease, variant plus phenotype, protein plus ligand, or pathway plus dataset\n- the user wants a synthesized answer rather than a single database lookup\n\n## Research Task Classification\n\nStart by classifying the request into one or more lanes:\n\n- human genetics and variant interpretation\n- locus-to-gene prioritization\n- expression, tissue, or cell-type context\n- pathway, network, or functional biology\n- protein structure and mechanism\n- chemistry, ligands, and pharmacology\n- clinical, translational, or cancer evidence\n- literature, preprints, and public dataset discovery\n- metabolomics, proteomics, or microbiome context\n\nPrefer 1 to 3 lanes. Only expand further if the user explicitly asks for a broad landscape review.\n\n## Entity Normalization\n\nNormalize the key entities before deep retrieval.\n\nCommon patterns:\n\n- gene or protein: `ncbi-clinicaltables-skill`, `ensembl-skill`, `uniprot-skill`\n- disease or phenotype: `efo-ontology-skill`, `opentargets-skill`\n- variant: `clinvar-variation-skill`, `ensembl-skill`, cohort-specific PheWAS skills\n- compound or metabolite: `chembl-skill`, `pubchem-pug-skill`, `chebi-skill`, `hmdb-skill`\n- pathway or function: `reactome-skill`, `quickgo-skill`, `string-skill`\n- accession or dataset identifier: `ncbi-datasets-skill`, `biostudies-arrayexpress-skill`, `pride-skill`, `metabolights-skill`\n\nDo not start broad evidence collection until the important entities are stable enough to route correctly.\n\n## Skill Selection Heuristics\n\nChoose the smallest set of skills that can answer the question well.\n\nExamples:\n\n- target or disease evidence review:\n  `opentargets-skill`, `gwas-catalog-skill`, `gtex-eqtl-skill`, `human-protein-atlas-skill`\n- variant interpretation:\n  `clinvar-variation-skill`, `gnomad-graphql-skill`, `ensembl-skill`, one or more cohort PheWAS skills\n- locus-to-gene mapping:\n  `locus-to-gene-mapper-skill`, or its component genetics skills when the user wants a custom workflow\n- structure and mechanism:\n  `alphafold-skill`, `rcsb-pdb-skill`, `uniprot-skill`, `reactome-skill`\n- chemistry and pharmacology:\n  `chembl-skill`, `bindingdb-skill`, `pubchem-pug-skill`, `pharmgkb-skill`\n- clinical and translational:\n  `clinicaltrials-skill`, `cbioportal-skill`, `civic-skill`\n- literature and dataset discovery:\n  `ncbi-entrez-skill`, `ncbi-pmc-skill`, `biorxiv-skill`, `biostudies-arrayexpress-skill`, `ncbi-datasets-skill`\n\nPrefer direct lookups before expensive multi-step chains.\n\n## Subagent And Parallelization Guidance\n\nIf Codex subagents are available, use them only when the work cleanly decomposes into independent lanes.\n\nGood candidates for subagents:\n\n- genetics, expression, structure, chemistry, and clinical evidence can be gathered independently for the same question\n- multiple loci, variants, genes, compounds, or datasets need parallel comparison\n- a broad landscape review requires separate evidence summaries before synthesis\n\nKeep these steps with the coordinating agent:\n\n- initial interpretation of the user request\n- entity normalization and final scope decisions\n- conflict resolution across evidence sources\n- final synthesis and recommendation writing\n\nAvoid subagents when:\n\n- one specific skill already answers the question\n- later steps depend tightly on earlier intermediate outputs\n- the work is mostly identifier resolution or narrow follow-up lookup\n- the extra coordination cost is likely to exceed the retrieval benefit\n\nWhen delegating, give each subagent a bounded read-only objective such as one evidence family or one comparison unit. Each subagent should return:\n\n- what it checked\n- the key findings\n- the main caveats\n- which skills or sources it used\n- any artifact paths it produced\n\nThe coordinating agent is responsible for reconciling overlaps, contradictions, and evidence gaps.\n\n## Output Contract\n\nReturn a concise answer structured around the user's question, not around the tools.\n\nUnless the user asks for a different format, include:\n\n1. direct answer or working conclusion\n2. key evidence by lane\n3. main caveats or unresolved questions\n4. recommended next analyses or follow-up lookups\n\nIf the task is exploratory, explicitly distinguish:\n\n- evidence that supports a conclusion\n- evidence that is only suggestive\n- evidence that is missing or contradictory\n\n## Operating Rules\n\n- prefer concise source-backed synthesis over large raw dumps\n- escalate to multi-skill workflows only when the question requires synthesis\n- state important cohort, ancestry, assay, tissue, and study-design limitations\n- do not overstate causality from association-only evidence\n- if a downstream skill can answer the request directly, hand off to it instead of keeping the router in the foreground\n",{"name":5,"description":7},"main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fresearch-router-skill","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zfifteen\u002Fskills-catalog --skill research-router-skill",{"tool":37,"command":38},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill research-router-skill",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill research-router-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch-router-skill\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",399,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch-router-skill\u002Fagents\u002Fopenai.yaml",[52,59,66,73,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]