[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7543AQPW2ASRSPW179BSA01":3,"skill-same:01M7543AQPW2ASRSPW179BSA01":55},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":54},"01M7543AQPW2ASRSPW179BSA01","nutrigenomics",null,"Curated single-marker evidence for declared nutrient-metabolism,\nfood-tolerance, and taste-perception domains. Refuses diet prescriptions,\nsupplement dosing, weight-loss prediction, methylation-cycle prescriptions,\nmicrobiome-mediated effects, and other out-of-scope nutrigenomic claims.","exon-research\u002Fgenomi","exon-research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F287072540?v=4","01M754130SK0JVWXNQKF8XANKV","Exon Research","01M754131W4AFK5CDRWT1KHP8X",492,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi\u002Fblob\u002Fmaster\u002Fskills\u002Fnutrigenomics\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: nutrigenomics\ndescription: |\n  Curated single-marker evidence for declared nutrient-metabolism,\n  food-tolerance, and taste-perception domains. Refuses diet prescriptions,\n  supplement dosing, weight-loss prediction, methylation-cycle prescriptions,\n  microbiome-mediated effects, and other out-of-scope nutrigenomic claims.\ntools:\n  - nutrigenomics.list_domains\n  - nutrigenomics.build_source_context\n  - nutrigenomics.retrieve_domain_markers\n  - nutrigenomics.retrieve_variant_records\n  - gnomad.fetch_population_frequency\n  - gwas.compare_variant_associations\nmutating: true\n---\n\n# Nutrigenomics\n\nUse this skill when the user asks how a germline variant affects nutrient\nmetabolism, food tolerance, or taste perception within declared domains:\n\n- folate metabolism\n- vitamin D status\n- iron storage\n- lactose tolerance\n- lipid diet response (APOE e2\u002Fe3\u002Fe4)\n- obesity predisposition (single-marker context only)\n\n## Out of scope — refuse, do not approximate\n\nDo NOT use this skill for, and DO surface as refusals:\n\n- Macronutrient ratio prescriptions (\"eat X% fat because of your APOE\")\n- Specific supplement dosing recommendations\n- Weight-loss outcome prediction from genotype\n- Diet-matching to genotype for fitness goals\n- Microbiome-mediated dietary effects\n- \"Methylation cycle\" prescriptions beyond folate marker context\n- General health-outcome prediction from a small marker set\n- \"Detox capacity\" framings\n- Food allergy risk prediction\n- Vitamin megadose prescriptions\n\nThe capability returns `coverage_status: out_of_scope_for_input` for these\ndomain ids. Treat the refusal literally — do not reach for adjacent records\nthat look similar.\n\n## Contract\n\n- Reads public catalogue metadata only; does not read an Active Genome Index.\n- For scanning an active genome, compose with\n  `active_genome_index.classify_genotype_support` using the variant\n  coordinates carried in each record.\n- For stratified allele frequencies, call `gnomad.fetch_population_frequency`.\n- For primary GWAS effect sizes, call `gwas.compare_variant_associations`\n  using the `gwas_catalog_id` carried in each record's\n  `downstream_traits_with_gwas`.\n\n> **Convention:** See `skills\u002Fconventions\u002Fcontext-routing.md`.\n> **Convention:** See `skills\u002Fconventions\u002Fevidence-quality.md`.\n> **Convention:** See `skills\u002F_output-rules.md`.\n\n## First Actions\n\n1. If the request is shaped like a diet prescription, supplement dosing,\n   weight-loss prediction, or any item in the out-of-scope list, refuse\n   first. Do not call retrieval tools.\n2. Use `nutrigenomics.list_domains` to confirm the relevant domain is\n   declared and to inspect evidence-tier counts before drilling in.\n3. Use `nutrigenomics.build_source_context` when grounding a discussion in\n   provenance is needed — e.g. when a user asks where the records come from\n   or why diet prescriptions are out of scope.\n4. Use `nutrigenomics.retrieve_domain_markers` with the validated\n   `domain_id`. Default `min_evidence_tier=\"established\"`. Loosen to\n   `\"probable\"` only when the question explicitly invites less-replicated\n   evidence.\n5. Use `nutrigenomics.retrieve_variant_records` when the agent already has\n   an rsID and wants to know which declared domains reference it.\n\n## Interpretation Rules\n\n- Each record carries `out_of_scope_claims`. Surface these as explicit\n  disclaimers — do not paraphrase around them.\n- `evidence_tier` is literal. An `emerging` record is not equivalent to an\n  `established` one; hedge in any agent-generated text accordingly.\n- Single-marker evidence does not substitute for measured lab values\n  (serum 25(OH)D, ferritin\u002Ftransferrin saturation, homocysteine, lipid panel)\n  when clinical decisions are at stake.\n- Absence of a marker from the catalogue is not evidence of negligible effect\n  — the catalogue is intentionally small and curated.\n\n## User-Facing Answer Shape\n\nDo not add a routine Active Genome Index status line for these public catalogue\ntools. For each cited marker:\n\n- Variant identifier (rsID + gene)\n- Established effect (single sentence)\n- Evidence tier\n- One or two of the most relevant `out_of_scope_claims` as disclaimers\n- The single most relevant lab measurement that should accompany the marker\n  (when applicable: homocysteine for MTHFR, 25(OH)D for vitamin D markers,\n  ferritin + transferrin saturation for HFE)\n\n## Cross-Capability Synthesis\n\nA scope-limited result from this capability is not a final user-facing answer\nwhen other Genomi capabilities can contribute orthogonal evidence to the same\nquestion. Returning \"cannot answer\" while applicable capabilities remain\nunexamined is a host-agent failure mode.\n\n## Tools\n\n### nutrigenomics.build_source_context\n\nExplain nutrigenomic catalogue provenance, domain definitions, evidence-tier meanings, method limitations, and the non-prescription boundary.\n\n**Use when**: The user or agent asks what the nutrigenomics catalogue is, where the records come from, what evidence tiers mean, or why the capability refuses diet prescriptions.\n\n**Why necessary**: Nutrigenomic language is easy to overstate. Explicit source context grounds the agent in the boundary before it interprets records.\n\n**Not for**: Returning marker records; use nutrigenomics.retrieve_domain_markers or nutrigenomics.retrieve_variant_records.\n\n**Example prompts**: Explain the source and limitations of Genomi's nutrigenomic catalogue.\n\n**Result semantics**: Public metadata only. Returns capability provenance, declared domains, evidence-tier definitions, out-of-scope-by-construction items, and the non-prescription boundary note.\n\n### nutrigenomics.list_domains\n\nList declared nutrigenomic domains with evidence-tier coverage and explicit out-of-scope-by-construction notes.\n\n**Use when**: The user asks what nutrigenomic domains Genomi covers, or the host agent needs to validate that a domain is in scope before retrieving markers.\n\n**Why necessary**: Nutrigenomics is a pseudoscience-prone domain. Listing declared domains and explicit out-of-scope-by-construction items lets the agent refuse out-of-scope questions before reaching for marker records.\n\n**Not for**: Returning specific marker records; use nutrigenomics.retrieve_domain_markers. Diet prescriptions, supplement dosing, weight-loss prediction.\n\n**Example prompts**: What nutrigenomic domains does Genomi cover? Is weight-loss diet matching in scope for Genomi nutrigenomics?\n\n**Result semantics**: Returns the declared domain catalogue, evidence-tier counts per domain, the out-of-scope-by-construction list, and the non-prescription boundary note.\n\n### nutrigenomics.retrieve_domain_markers\n\nRetrieve curated single-marker records for a declared nutrigenomic domain, filtered by minimum evidence tier.\n\n**Use when**: The host agent needs curated single-marker evidence for a declared domain (folate_metabolism, lactose_tolerance, iron_storage, vitamin_d_status, lipid_diet_response, obesity_predisposition).\n\n**Why necessary**: Returns evidence-tiered records with explicit out_of_scope_claims so the agent can ground a nutrient\u002Ftolerance discussion without propagating pseudoscience claims about the variant.\n\n**Not for**: Diet prescriptions, supplement dosing, weight-loss prediction. Polygenic risk scoring; this is single-marker evidence only. Genome scanning; compose with active_genome_index.classify_genotype_support using the variant coordinates from each record. Population-stratified allele frequencies; use gnomad.fetch_population_frequency. Primary GWAS effect sizes; use gwas.compare_variant_associations with the gwas_catalog_id from downstream_traits_with_gwas.\n\n**Example prompts**: What does Genomi have on folate_metabolism markers? Retrieve established-tier iron_storage records.\n\n**Result semantics**: Each record carries variant identifiers, established_effect with GWAS Catalog chain-out, evidence_tier, resolvable source citations, established_caveats, and out_of_scope_claims. The agent must surface out_of_scope_claims as disclaimers rather than paraphrase around them.\n\n### nutrigenomics.retrieve_variant_records\n\nRetrieve any nutrigenomic catalogue records referencing a specific rsID.\n\n**Use when**: The host agent has a specific variant identifier and wants to know whether the nutrigenomic catalogue carries any records for it.\n\n**Why necessary**: A variant may participate in more than one declared domain. Variant-anchored lookup surfaces all matching curated records at once.\n\n**Not for**: Variant resolution from coordinate to rsID; use variant.resolve first. Variants outside declared nutrigenomic domains; in_scope_empty indicates the catalogue does not cover the variant.\n\n**Example prompts**: What does Genomi say about rs1801133 nutrigenomically? Are there nutrigenomic records for rs429358?\n\n**Result semantics**: Returns one or more curated records referencing the variant. coverage_status='in_scope_empty' when the variant is not in the catalogue; absence is not evidence of negligible effect.\n","# Nutrigenomics\n\nUse this skill when the user asks how a germline variant affects nutrient\nmetabolism, food tolerance, or taste perception within declared domains:\n\n- folate metabolism\n- vitamin D status\n- iron storage\n- lactose tolerance\n- lipid diet response (APOE e2\u002Fe3\u002Fe4)\n- obesity predisposition (single-marker context only)\n\n## Out of scope — refuse, do not approximate\n\nDo NOT use this skill for, and DO surface as refusals:\n\n- Macronutrient ratio prescriptions (\"eat X% fat because of your APOE\")\n- Specific supplement dosing recommendations\n- Weight-loss outcome prediction from genotype\n- Diet-matching to genotype for fitness goals\n- Microbiome-mediated dietary effects\n- \"Methylation cycle\" prescriptions beyond folate marker context\n- General health-outcome prediction from a small marker set\n- \"Detox capacity\" framings\n- Food allergy risk prediction\n- Vitamin megadose prescriptions\n\nThe capability returns `coverage_status: out_of_scope_for_input` for these\ndomain ids. Treat the refusal literally — do not reach for adjacent records\nthat look similar.\n\n## Contract\n\n- Reads public catalogue metadata only; does not read an Active Genome Index.\n- For scanning an active genome, compose with\n  `active_genome_index.classify_genotype_support` using the variant\n  coordinates carried in each record.\n- For stratified allele frequencies, call `gnomad.fetch_population_frequency`.\n- For primary GWAS effect sizes, call `gwas.compare_variant_associations`\n  using the `gwas_catalog_id` carried in each record's\n  `downstream_traits_with_gwas`.\n\n> **Convention:** See `skills\u002Fconventions\u002Fcontext-routing.md`.\n> **Convention:** See `skills\u002Fconventions\u002Fevidence-quality.md`.\n> **Convention:** See `skills\u002F_output-rules.md`.\n\n## First Actions\n\n1. If the request is shaped like a diet prescription, supplement dosing,\n   weight-loss prediction, or any item in the out-of-scope list, refuse\n   first. Do not call retrieval tools.\n2. Use `nutrigenomics.list_domains` to confirm the relevant domain is\n   declared and to inspect evidence-tier counts before drilling in.\n3. Use `nutrigenomics.build_source_context` when grounding a discussion in\n   provenance is needed — e.g. when a user asks where the records come from\n   or why diet prescriptions are out of scope.\n4. Use `nutrigenomics.retrieve_domain_markers` with the validated\n   `domain_id`. Default `min_evidence_tier=\"established\"`. Loosen to\n   `\"probable\"` only when the question explicitly invites less-replicated\n   evidence.\n5. Use `nutrigenomics.retrieve_variant_records` when the agent already has\n   an rsID and wants to know which declared domains reference it.\n\n## Interpretation Rules\n\n- Each record carries `out_of_scope_claims`. Surface these as explicit\n  disclaimers — do not paraphrase around them.\n- `evidence_tier` is literal. An `emerging` record is not equivalent to an\n  `established` one; hedge in any agent-generated text accordingly.\n- Single-marker evidence does not substitute for measured lab values\n  (serum 25(OH)D, ferritin\u002Ftransferrin saturation, homocysteine, lipid panel)\n  when clinical decisions are at stake.\n- Absence of a marker from the catalogue is not evidence of negligible effect\n  — the catalogue is intentionally small and curated.\n\n## User-Facing Answer Shape\n\nDo not add a routine Active Genome Index status line for these public catalogue\ntools. For each cited marker:\n\n- Variant identifier (rsID + gene)\n- Established effect (single sentence)\n- Evidence tier\n- One or two of the most relevant `out_of_scope_claims` as disclaimers\n- The single most relevant lab measurement that should accompany the marker\n  (when applicable: homocysteine for MTHFR, 25(OH)D for vitamin D markers,\n  ferritin + transferrin saturation for HFE)\n\n## Cross-Capability Synthesis\n\nA scope-limited result from this capability is not a final user-facing answer\nwhen other Genomi capabilities can contribute orthogonal evidence to the same\nquestion. Returning \"cannot answer\" while applicable capabilities remain\nunexamined is a host-agent failure mode.\n\n## Tools\n\n### nutrigenomics.build_source_context\n\nExplain nutrigenomic catalogue provenance, domain definitions, evidence-tier meanings, method limitations, and the non-prescription boundary.\n\n**Use when**: The user or agent asks what the nutrigenomics catalogue is, where the records come from, what evidence tiers mean, or why the capability refuses diet prescriptions.\n\n**Why necessary**: Nutrigenomic language is easy to overstate. Explicit source context grounds the agent in the boundary before it interprets records.\n\n**Not for**: Returning marker records; use nutrigenomics.retrieve_domain_markers or nutrigenomics.retrieve_variant_records.\n\n**Example prompts**: Explain the source and limitations of Genomi's nutrigenomic catalogue.\n\n**Result semantics**: Public metadata only. Returns capability provenance, declared domains, evidence-tier definitions, out-of-scope-by-construction items, and the non-prescription boundary note.\n\n### nutrigenomics.list_domains\n\nList declared nutrigenomic domains with evidence-tier coverage and explicit out-of-scope-by-construction notes.\n\n**Use when**: The user asks what nutrigenomic domains Genomi covers, or the host agent needs to validate that a domain is in scope before retrieving markers.\n\n**Why necessary**: Nutrigenomics is a pseudoscience-prone domain. Listing declared domains and explicit out-of-scope-by-construction items lets the agent refuse out-of-scope questions before reaching for marker records.\n\n**Not for**: Returning specific marker records; use nutrigenomics.retrieve_domain_markers. Diet prescriptions, supplement dosing, weight-loss prediction.\n\n**Example prompts**: What nutrigenomic domains does Genomi cover? Is weight-loss diet matching in scope for Genomi nutrigenomics?\n\n**Result semantics**: Returns the declared domain catalogue, evidence-tier counts per domain, the out-of-scope-by-construction list, and the non-prescription boundary note.\n\n### nutrigenomics.retrieve_domain_markers\n\nRetrieve curated single-marker records for a declared nutrigenomic domain, filtered by minimum evidence tier.\n\n**Use when**: The host agent needs curated single-marker evidence for a declared domain (folate_metabolism, lactose_tolerance, iron_storage, vitamin_d_status, lipid_diet_response, obesity_predisposition).\n\n**Why necessary**: Returns evidence-tiered records with explicit out_of_scope_claims so the agent can ground a nutrient\u002Ftolerance discussion without propagating pseudoscience claims about the variant.\n\n**Not for**: Diet prescriptions, supplement dosing, weight-loss prediction. Polygenic risk scoring; this is single-marker evidence only. Genome scanning; compose with active_genome_index.classify_genotype_support using the variant coordinates from each record. Population-stratified allele frequencies; use gnomad.fetch_population_frequency. Primary GWAS effect sizes; use gwas.compare_variant_associations with the gwas_catalog_id from downstream_traits_with_gwas.\n\n**Example prompts**: What does Genomi have on folate_metabolism markers? Retrieve established-tier iron_storage records.\n\n**Result semantics**: Each record carries variant identifiers, established_effect with GWAS Catalog chain-out, evidence_tier, resolvable source citations, established_caveats, and out_of_scope_claims. The agent must surface out_of_scope_claims as disclaimers rather than paraphrase around them.\n\n### nutrigenomics.retrieve_variant_records\n\nRetrieve any nutrigenomic catalogue records referencing a specific rsID.\n\n**Use when**: The host agent has a specific variant identifier and wants to know whether the nutrigenomic catalogue carries any records for it.\n\n**Why necessary**: A variant may participate in more than one declared domain. Variant-anchored lookup surfaces all matching curated records at once.\n\n**Not for**: Variant resolution from coordinate to rsID; use variant.resolve first. Variants outside declared nutrigenomic domains; in_scope_empty indicates the catalogue does not cover the variant.\n\n**Example prompts**: What does Genomi say about rs1801133 nutrigenomically? Are there nutrigenomic records for rs429358?\n\n**Result semantics**: Returns one or more curated records referencing the variant. coverage_status='in_scope_empty' when the variant is not in the catalogue; absence is not evidence of negligible effect.\n",{"name":5,"tools":24,"mutating":31,"description":32},[25,26,27,28,29,30],"nutrigenomics.list_domains","nutrigenomics.build_source_context","nutrigenomics.retrieve_domain_markers","nutrigenomics.retrieve_variant_records","gnomad.fetch_population_frequency","gwas.compare_variant_associations",true,"Curated single-marker evidence for declared nutrient-metabolism,\nfood-tolerance, and taste-perception domains. Refuses diet prescriptions,\nsupplement dosing, weight-loss prediction, methylation-cycle prescriptions,\nmicrobiome-mediated effects, and other out-of-scope nutrigenomic claims.\n","master","1df4f5bfb635e2d08f93a1102b70b840fbe80d86","skills\u002Fnutrigenomics",61,"https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi","https:\u002F\u002Fwww.genomiagent.com\u002F","https:\u002F\u002Fgithub.com\u002Fexon-research","Building local-first AI co-scientist for genomic research","2026-09-01 03:30:56",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":31},[44,47,50],{"tool":45,"command":46},"npx","npx skills add exon-research\u002Fgenomi --skill nutrigenomics",{"tool":48,"command":49},"bunx","bunx skills add exon-research\u002Fgenomi --skill nutrigenomics",{"tool":51,"command":52},"pnpm","pnpm dlx skills add exon-research\u002Fgenomi --skill nutrigenomics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi\u002Fblob\u002Fmaster\u002Fskills\u002Fnutrigenomics\u002FSKILL.md",[],[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75442YT3ZG6MG47E5MJ3HG2","variant-evidence","Answer specific rsID, allele, gene, region, genotype, and absence\u002Fcallability\nquestions using explicit session context or public evidence.","https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi\u002Fblob\u002Fmaster\u002Fskills\u002Fvariant-evidence\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M754400MW6S0MEN19S4CM9DE","journal-source-research","Journal sub-skill for focused public\u002Fsource evidence review and reviewed\nfinding write-back before interpretation or answer synthesis.","https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi\u002Fblob\u002Fmaster\u002Fskills\u002Fsource-research\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7543X67TA0MBK3YGC0NJAX9","sequence","Deterministic sequence utilities for translation, ORFs, restriction sites,\nKozak context, primer checks, and local FASTA record matching.","https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi\u002Fblob\u002Fmaster\u002Fskills\u002Fsequence\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7543RHCHF4WJ69P0K0QTTFB","rare-disease-cancer","Plan rare disease, hereditary disease, cancer risk, carrier-relevance, and\nobserved-condition source investigation from public targets or selected\nactive genome evidence.","https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi\u002Fblob\u002Fmaster\u002Fskills\u002Frare-disease-cancer\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7543NDTVZB8T3RQBD0RK3MC","prs","Apply published polygenic scores from PGS Catalog to approved local personal DNA and return raw weighted score plus overlap QC.","https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi\u002Fblob\u002Fmaster\u002Fskills\u002Fprs\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7543FDFTWSYVVTEGHQSPHQK","pharmacogenomics","Answer drug-response, medication, PharmGKB-style, PGxDB, ATC, DrugBank,\ngene-drug, and variant-drug questions using public PGx evidence plus local\nsample genotype support when an Active Genome Index is selected.","https:\u002F\u002Fgithub.com\u002Fexon-research\u002Fgenomi\u002Fblob\u002Fmaster\u002Fskills\u002Fpharmacogenomics\u002FSKILL.md",[],[]]