[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QGRHZNKWXB18ZCPFE33F7F":3,"skill-same:01M6QGRHZNKWXB18ZCPFE33F7F":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":14,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6QGRHZNKWXB18ZCPFE33F7F","folklore-variant-evidence",null,"Retrieves ClinGen gene-disease validity assertions for a public gene or disease, and reviews source-linked public evidence and literature for one supported GRCh38 germline nuclear SNV or simple indel through Folklore Clinical Variant Interpretation MCP. Used when a scientific agent must branch deterministically on resolved, ambiguous, not-found, invalid, unsupported, or unavailable variant outcomes; chain a resolved public variant into related literature or publication details; or preserve evidence provenance without accepting patient, phenotype, family, segregation, or private case data.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkd-folklore-variant-evidence\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"variant","evidence","folklore variant evidence","indel","gene","for","reviews","scientific","post","case","literature","MCP","snv","evidence provenance","host","invalid","family","outcomes","branch","provenance","2026-11-10 10:12:30",false,"---\nname: folklore-variant-evidence\ndescription: \"Retrieves ClinGen gene-disease validity assertions for a public gene or disease, and reviews source-linked public evidence and literature for one supported GRCh38 germline nuclear SNV or simple indel through Folklore Clinical Variant Interpretation MCP. Used when a scientific agent must branch deterministically on resolved, ambiguous, not-found, invalid, unsupported, or unavailable variant outcomes; chain a resolved public variant into related literature or publication details; or preserve evidence provenance without accepting patient, phenotype, family, segregation, or private case data.\"\nlicense: MIT\ncompatibility: Requires network access to api.helena.bio (stateless Streamable HTTP MCP, no credentials) and a host supporting its advertised protocol, or curl for direct JSON-RPC POST requests.\nmetadata:\n  version: \"1.2\"\n  last-reviewed: \"2026-09-30\"\n  skill-author: \"Helena Bioinformatics\"\n  website: \"https:\u002F\u002Ffolklore.helena.bio\"\n  github: \"https:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp\"\ncategory: \"scientific-computing\"\n---\n\n# Folklore Variant Evidence\n\nUse Folklore Clinical Variant Interpretation MCP to retrieve structured public\nvariant evidence, automated variant-level ACMG\u002FAMP decision support, provenance,\nand source-linked literature for professional review. Keep the workflow limited\nto public identifiers and preserve every explicit outcome state. Adapter 1.5.0 also provides ClinGen Gene-Disease Validity assertions; source coverage is bounded, not every known association.\n\nFolklore Clinical Variant Interpretation MCP is published by Helena\nBioinformatics. Its hosted endpoint is:\n\n```text\nhttps:\u002F\u002Fapi.helena.bio\u002Ffolklore\u002Fv1\u002Fmcp\n```\n\nNo account or API key is required. The public Apache-2.0 adapter and contract are\navailable at \u003Chttps:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp>.\n\n## Minimal connection example\n\nA host without native MCP support can make the same public JSON-RPC call:\n\n```bash\ncurl --silent --show-error --fail-with-body --max-time 60 \\\n  -X POST https:\u002F\u002Fapi.helena.bio\u002Ffolklore\u002Fv1\u002Fmcp \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -H 'Accept: application\u002Fjson, text\u002Fevent-stream' \\\n  -H 'MCP-Protocol-Version: 2026-07-28' \\\n  -H 'Mcp-Method: tools\u002Fcall' \\\n  -H 'Mcp-Name: search_variant_evidence' \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Fcall\",\"params\":{\"_meta\":{\"io.modelcontextprotocol\u002FprotocolVersion\":\"2026-07-28\",\"io.modelcontextprotocol\u002FclientCapabilities\":{}},\"name\":\"search_variant_evidence\",\"arguments\":{\"assembly\":\"GRCh38\",\"query\":\"rs80357914\"}}}'\n```\n\nThe routing headers must match the JSON-RPC method and tool name. A successful\nHTTP response is not sufficient: inspect JSON-RPC `error`, then\n`result.structuredContent.adapter_error`, then this tool's\n`result.structuredContent.result.status`. Other tools use different response\nshapes; use the [contract table](references\u002Fmcp-contract.md).\n\nInspect the returned outcome before continuing. This example can return\n`ambiguous` with multiple candidates: stop and request an unambiguous public\nvariant notation instead of selecting a candidate automatically.\n\n## Select the right skill\n\nUse this skill when the task is one public variant to structured Folklore\nevidence, explicit resolution-state handling, variant-linked literature, or ClinGen gene-to-disease\u002Fdisease-to-gene assertions.\n\n- Use `database-lookup` for broad direct queries across ClinVar, dbSNP, gnomAD,\n  Ensembl VEP, COSMIC, or multiple databases.\n- Use `genomic-coordinates` first when the assembly, coordinate convention,\n  contig name, or variant representation is uncertain.\n- Do not use this skill for VCF annotation, batch processing, somatic variants,\n  structural variants, polygenic scores, or patient-specific interpretation.\n\nFolklore Clinical Variant Interpretation MCP complements those skills with one\nsource-linked public evidence contract. It does not replace direct database\nreview or qualified clinical judgment.\n\n## Enforce the input boundary\n\nBefore a variant tool call:\n\n1. Extract exactly one public variant identifier or notation.\n2. Require GRCh38 and a germline nuclear SNV or simple insertion\u002Fdeletion shorter\n   than 50 base pairs. An unsupported assembly may be rejected by the input\n   schema before any scientific `unsupported` status exists.\n3. Remove or refuse patient names, case identifiers, phenotypes, family history,\n   segregation evidence, clinical records, uploaded files, and other private or\n   patient-specific context.\n4. If the task depends on patient context, stop and explain that Folklore\n   Clinical Variant Interpretation MCP does not accept or evaluate it.\n5. Never transform a patient-specific request into a public variant query while\n   implying that the result answers the patient-specific question.\n\nAccepted public variant forms include genomic coordinates, genomic\u002Fcoding\u002F\nprotein HGVS, SPDI, rsID, or a `canonical_key` returned by Folklore Clinical\nVariant Interpretation MCP.\n\n## Verify the live tool catalog\n\nConnect to the hosted endpoint and call `tools\u002Flist`. Verify the available tools\ninstead of relying on model memory. The documented public catalog contains:\n\n- `search_variant_evidence`\n- `search_variant_literature`\n- `get_publication_details`\n- `search_literature_corpus`\n- `get_gene_disease_associations`\n- `search_disease_genes`\n\nThe separate seventh tool `support_helena` is not scientific evidence; use it only when explicitly requested.\n\nIf discovery or a tool call fails, preserve the failure as an availability\nproblem. Do not reinterpret it as lack of scientific evidence.\n\nRead [the public MCP contract](references\u002Fmcp-contract.md) before composing tool\ncalls or interpreting response states.\n\n## Retrieve gene-disease assertions\n\nUse `get_gene_disease_associations` for one exact gene symbol or HGNC identifier, or `search_disease_genes` for an exact MONDO identifier or public disease-name substring. Both accept `limit` (default 20, 1–50) and `offset` (default 0, 0–1000). See the reference for request examples. This is a separate source lookup and requires no variant input or assembly.\n\nPreserve each returned disease identity, inheritance, evidence assessment, source\nURL, date, `source.version` and `source.snapshotSha256`. This is a local ClinGen\nsnapshot, not a guarantee of the latest ClinGen release. Follow\n`pagination.nextOffset` while it is present; preserve pagination-ceiling warnings.\nAn empty page after the total has been passed does not mean the initial query had\nno matches. Do not combine distinct diseases or silently choose among name matches.\nGene-disease validity does not classify a particular variant. A `not_found`\nresponse means no matching assertion in the available source, not no association.\nNo patient, phenotype, family, segregation, private case data or sequencing files\nmay be sent. Qualified professional review remains required.\n\n## Run the variant-evidence workflow\n\n### 1. Resolve and retrieve evidence\n\nCall `search_variant_evidence` with:\n\n```text\nassembly: GRCh38\nquery: \u003Cone public variant identifier or notation>\n```\n\nDo not add phenotype, disease, patient, family, or treatment context to this\ncall. Preserve the returned contract fields, source links, limitations, and\nusage boundary.\n\n### 2. Branch on the returned status\n\nRead transport\u002FJSON-RPC errors and `adapter_error` first. For\n`search_variant_evidence`, let `envelope = result.structuredContent`; only if\n`envelope.result` is non-null, branch on `envelope.result.status`. An\n`invalid_arguments` adapter error is distinct from scientific `invalid_request`.\nPreserve `isError` and any typed failure, including `resolution_unavailable`.\nTreat the status as a control-flow value, not prose:\n\n| Status | Required action |\n|---|---|\n| `resolved` | Reuse the returned `canonical_key`; review the structured interpretation, provenance, source links, and limitations. |\n| `ambiguous` | Show the returned candidates and ask for an explicit public variant selection. Never choose a candidate automatically. |\n| `not_found` | Report that no result was found within this service and query scope. Do not claim universal absence. |\n| `invalid_request` | Report the validation problem and request a corrected public variant. Do not silently reinterpret the input. |\n| `unsupported` | State the relevant service boundary and stop. Do not force the query into a supported form. |\n| `resolution_unavailable` | Report a temporary resolution or availability failure. Do not treat it as evidence absence. |\n\nOnly a `resolved` result may proceed automatically into a variant-linked\nliterature workflow. Its canonical key is `envelope.result.identity.canonical_key`.\nIf `envelope.result.interpretation.status` is `unavailable`, preserve its typed\nerror; identity resolution has succeeded, but classification has not. Do not read\nor invent a classification for that outcome.\n\n### 3. Review the evidence without overclaiming\n\nFor a resolved result:\n\n- Present the returned variant identity and `canonical_key`.\n- Preserve the automated variant-level ACMG\u002FAMP decision-support result exactly\n  as returned.\n- Cite the returned public sources and provenance.\n- Keep submitted ClinVar assertions separate from Folklore's automated result,\n  as required by the [upstream interpretation guidance](https:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp).\n  If they disagree, report each assertion with its source\u002Fdate and preserve\n  the disagreement; do not present a merged consensus classification.\n- Separate returned facts from the agent's synthesis.\n- State that qualified professional review is required.\n- Do not turn the result into a diagnosis, individual risk estimate, treatment\n  recommendation, or standalone clinical report.\n\n## Chain into literature\n\n### Variant-linked literature\n\nAfter a resolved evidence call, pass the returned `canonical_key` to\n`search_variant_literature`. Keep `assembly` as `GRCh38`. An optional `question`\nmay narrow the literature focus, but it must remain a public scientific question\nand must not contain patient context.\n\nDistinguish each result's match type:\n\n- `exact_variant`: direct match to the resolved variant\n- `variant_alias`: match through a reported alias\n- `gene_association`: broader gene-level association, not variant-specific proof\n\nLiterature associations do not alter the returned ACMG\u002FAMP classification.\n\n### Publication details\n\nCall `get_publication_details` only with a PMID returned by the literature tools.\nPreserve PubMed URLs, DOI\u002FPMCID fields when present, retraction status, and the\ndistinction between gene mentions and variant mentions.\n\n### Semantic corpus search\n\nUse `search_literature_corpus` for a public natural-language scientific question\nor for discovery by publication identifier, gene, variant, phenotype, HPO, or\nOMIM concept. Treat results as source-linked candidates for professional review.\nA zero-result response means no result was returned for that bounded query, not\nthat no relevant publication exists anywhere.\n\nThe query is 3–200 characters, with `limit` 1–25 and `sort` set to `relevance`,\n`newest`, or `oldest`. For another page, reuse the returned opaque `next_cursor`\nwith the same query and sort; do not construct an offset. Keep `match_types` and\n`article_entities` distinct from variant-literature match types. Report\n`semantic_index_used` and `semantic_degraded_reason`; a returned lexical match\ndoes not prove semantic retrieval worked. Preserve additional retrieval metadata\nreturned by the live service.\n\nDo not place patient information into a corpus query, even if the query is not\nvariant-specific.\n\n## Report a reproducible result\n\nInclude:\n\n1. The exact public query and `GRCh38` assembly.\n2. The returned status and, if resolved, the `canonical_key`.\n3. The structured evidence or literature result without changing its meaning.\n4. Source links and publication identifiers.\n5. Match type for literature results.\n6. Access date and any availability limitation.\n7. This boundary statement:\n\n> This is public, variant-level decision support for qualified professional\n> review. It does not evaluate patient, phenotype, family, segregation, or\n> private case data and is not a diagnosis or treatment recommendation.\n\n## Falsifiable smoke test\n\nUse the public rsID `rs80357914` to test ambiguity handling:\n\n```text\nCall search_variant_evidence with assembly GRCh38 and query rs80357914. If the\nresult is ambiguous, list the returned candidates and stop for explicit\nselection. Do not select a candidate or call downstream literature tools.\n```\n\nThe ambiguity branch passes only if an ambiguous response causes the workflow to\nstop without automatic candidate selection. If the live response changes, record\nthe actual status; a resolved response does not test ambiguity handling.\n\nOn 2026-09-30, live discovery reported adapter 1.5.0 and protocol 2026-07-28.\nThe rsID example returned `ambiguous`; a separate public HGVS query resolved and\nwas chained through its returned key to literature and a returned PMID. Corpus\ncursor pagination and gene-disease offset pagination were exercised. These are\ndated protocol checks, not validation of clinical accuracy. See the reference\nfor exact response shapes and source\u002Flive differences.\n\n## Official references\n\n- Integration setup: \u003Chttps:\u002F\u002Ffolklore.helena.bio\u002Fintegrations>\n- Technical guide: \u003Chttps:\u002F\u002Ffolklore.helena.bio\u002Fdocs\u002Ffolklore-connector>\n- Public adapter and contract: \u003Chttps:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp>\n- Official MCP Registry identity: `io.github.helena-bioinformatics\u002Ffolklore`\n","# Folklore Variant Evidence\n\nUse Folklore Clinical Variant Interpretation MCP to retrieve structured public\nvariant evidence, automated variant-level ACMG\u002FAMP decision support, provenance,\nand source-linked literature for professional review. Keep the workflow limited\nto public identifiers and preserve every explicit outcome state. Adapter 1.5.0 also provides ClinGen Gene-Disease Validity assertions; source coverage is bounded, not every known association.\n\nFolklore Clinical Variant Interpretation MCP is published by Helena\nBioinformatics. Its hosted endpoint is:\n\n```text\nhttps:\u002F\u002Fapi.helena.bio\u002Ffolklore\u002Fv1\u002Fmcp\n```\n\nNo account or API key is required. The public Apache-2.0 adapter and contract are\navailable at \u003Chttps:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp>.\n\n## Minimal connection example\n\nA host without native MCP support can make the same public JSON-RPC call:\n\n```bash\ncurl --silent --show-error --fail-with-body --max-time 60 \\\n  -X POST https:\u002F\u002Fapi.helena.bio\u002Ffolklore\u002Fv1\u002Fmcp \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -H 'Accept: application\u002Fjson, text\u002Fevent-stream' \\\n  -H 'MCP-Protocol-Version: 2026-07-28' \\\n  -H 'Mcp-Method: tools\u002Fcall' \\\n  -H 'Mcp-Name: search_variant_evidence' \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Fcall\",\"params\":{\"_meta\":{\"io.modelcontextprotocol\u002FprotocolVersion\":\"2026-07-28\",\"io.modelcontextprotocol\u002FclientCapabilities\":{}},\"name\":\"search_variant_evidence\",\"arguments\":{\"assembly\":\"GRCh38\",\"query\":\"rs80357914\"}}}'\n```\n\nThe routing headers must match the JSON-RPC method and tool name. A successful\nHTTP response is not sufficient: inspect JSON-RPC `error`, then\n`result.structuredContent.adapter_error`, then this tool's\n`result.structuredContent.result.status`. Other tools use different response\nshapes; use the [contract table](references\u002Fmcp-contract.md).\n\nInspect the returned outcome before continuing. This example can return\n`ambiguous` with multiple candidates: stop and request an unambiguous public\nvariant notation instead of selecting a candidate automatically.\n\n## Select the right skill\n\nUse this skill when the task is one public variant to structured Folklore\nevidence, explicit resolution-state handling, variant-linked literature, or ClinGen gene-to-disease\u002Fdisease-to-gene assertions.\n\n- Use `database-lookup` for broad direct queries across ClinVar, dbSNP, gnomAD,\n  Ensembl VEP, COSMIC, or multiple databases.\n- Use `genomic-coordinates` first when the assembly, coordinate convention,\n  contig name, or variant representation is uncertain.\n- Do not use this skill for VCF annotation, batch processing, somatic variants,\n  structural variants, polygenic scores, or patient-specific interpretation.\n\nFolklore Clinical Variant Interpretation MCP complements those skills with one\nsource-linked public evidence contract. It does not replace direct database\nreview or qualified clinical judgment.\n\n## Enforce the input boundary\n\nBefore a variant tool call:\n\n1. Extract exactly one public variant identifier or notation.\n2. Require GRCh38 and a germline nuclear SNV or simple insertion\u002Fdeletion shorter\n   than 50 base pairs. An unsupported assembly may be rejected by the input\n   schema before any scientific `unsupported` status exists.\n3. Remove or refuse patient names, case identifiers, phenotypes, family history,\n   segregation evidence, clinical records, uploaded files, and other private or\n   patient-specific context.\n4. If the task depends on patient context, stop and explain that Folklore\n   Clinical Variant Interpretation MCP does not accept or evaluate it.\n5. Never transform a patient-specific request into a public variant query while\n   implying that the result answers the patient-specific question.\n\nAccepted public variant forms include genomic coordinates, genomic\u002Fcoding\u002F\nprotein HGVS, SPDI, rsID, or a `canonical_key` returned by Folklore Clinical\nVariant Interpretation MCP.\n\n## Verify the live tool catalog\n\nConnect to the hosted endpoint and call `tools\u002Flist`. Verify the available tools\ninstead of relying on model memory. The documented public catalog contains:\n\n- `search_variant_evidence`\n- `search_variant_literature`\n- `get_publication_details`\n- `search_literature_corpus`\n- `get_gene_disease_associations`\n- `search_disease_genes`\n\nThe separate seventh tool `support_helena` is not scientific evidence; use it only when explicitly requested.\n\nIf discovery or a tool call fails, preserve the failure as an availability\nproblem. Do not reinterpret it as lack of scientific evidence.\n\nRead [the public MCP contract](references\u002Fmcp-contract.md) before composing tool\ncalls or interpreting response states.\n\n## Retrieve gene-disease assertions\n\nUse `get_gene_disease_associations` for one exact gene symbol or HGNC identifier, or `search_disease_genes` for an exact MONDO identifier or public disease-name substring. Both accept `limit` (default 20, 1–50) and `offset` (default 0, 0–1000). See the reference for request examples. This is a separate source lookup and requires no variant input or assembly.\n\nPreserve each returned disease identity, inheritance, evidence assessment, source\nURL, date, `source.version` and `source.snapshotSha256`. This is a local ClinGen\nsnapshot, not a guarantee of the latest ClinGen release. Follow\n`pagination.nextOffset` while it is present; preserve pagination-ceiling warnings.\nAn empty page after the total has been passed does not mean the initial query had\nno matches. Do not combine distinct diseases or silently choose among name matches.\nGene-disease validity does not classify a particular variant. A `not_found`\nresponse means no matching assertion in the available source, not no association.\nNo patient, phenotype, family, segregation, private case data or sequencing files\nmay be sent. Qualified professional review remains required.\n\n## Run the variant-evidence workflow\n\n### 1. Resolve and retrieve evidence\n\nCall `search_variant_evidence` with:\n\n```text\nassembly: GRCh38\nquery: \u003Cone public variant identifier or notation>\n```\n\nDo not add phenotype, disease, patient, family, or treatment context to this\ncall. Preserve the returned contract fields, source links, limitations, and\nusage boundary.\n\n### 2. Branch on the returned status\n\nRead transport\u002FJSON-RPC errors and `adapter_error` first. For\n`search_variant_evidence`, let `envelope = result.structuredContent`; only if\n`envelope.result` is non-null, branch on `envelope.result.status`. An\n`invalid_arguments` adapter error is distinct from scientific `invalid_request`.\nPreserve `isError` and any typed failure, including `resolution_unavailable`.\nTreat the status as a control-flow value, not prose:\n\n| Status | Required action |\n|---|---|\n| `resolved` | Reuse the returned `canonical_key`; review the structured interpretation, provenance, source links, and limitations. |\n| `ambiguous` | Show the returned candidates and ask for an explicit public variant selection. Never choose a candidate automatically. |\n| `not_found` | Report that no result was found within this service and query scope. Do not claim universal absence. |\n| `invalid_request` | Report the validation problem and request a corrected public variant. Do not silently reinterpret the input. |\n| `unsupported` | State the relevant service boundary and stop. Do not force the query into a supported form. |\n| `resolution_unavailable` | Report a temporary resolution or availability failure. Do not treat it as evidence absence. |\n\nOnly a `resolved` result may proceed automatically into a variant-linked\nliterature workflow. Its canonical key is `envelope.result.identity.canonical_key`.\nIf `envelope.result.interpretation.status` is `unavailable`, preserve its typed\nerror; identity resolution has succeeded, but classification has not. Do not read\nor invent a classification for that outcome.\n\n### 3. Review the evidence without overclaiming\n\nFor a resolved result:\n\n- Present the returned variant identity and `canonical_key`.\n- Preserve the automated variant-level ACMG\u002FAMP decision-support result exactly\n  as returned.\n- Cite the returned public sources and provenance.\n- Keep submitted ClinVar assertions separate from Folklore's automated result,\n  as required by the [upstream interpretation guidance](https:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp).\n  If they disagree, report each assertion with its source\u002Fdate and preserve\n  the disagreement; do not present a merged consensus classification.\n- Separate returned facts from the agent's synthesis.\n- State that qualified professional review is required.\n- Do not turn the result into a diagnosis, individual risk estimate, treatment\n  recommendation, or standalone clinical report.\n\n## Chain into literature\n\n### Variant-linked literature\n\nAfter a resolved evidence call, pass the returned `canonical_key` to\n`search_variant_literature`. Keep `assembly` as `GRCh38`. An optional `question`\nmay narrow the literature focus, but it must remain a public scientific question\nand must not contain patient context.\n\nDistinguish each result's match type:\n\n- `exact_variant`: direct match to the resolved variant\n- `variant_alias`: match through a reported alias\n- `gene_association`: broader gene-level association, not variant-specific proof\n\nLiterature associations do not alter the returned ACMG\u002FAMP classification.\n\n### Publication details\n\nCall `get_publication_details` only with a PMID returned by the literature tools.\nPreserve PubMed URLs, DOI\u002FPMCID fields when present, retraction status, and the\ndistinction between gene mentions and variant mentions.\n\n### Semantic corpus search\n\nUse `search_literature_corpus` for a public natural-language scientific question\nor for discovery by publication identifier, gene, variant, phenotype, HPO, or\nOMIM concept. Treat results as source-linked candidates for professional review.\nA zero-result response means no result was returned for that bounded query, not\nthat no relevant publication exists anywhere.\n\nThe query is 3–200 characters, with `limit` 1–25 and `sort` set to `relevance`,\n`newest`, or `oldest`. For another page, reuse the returned opaque `next_cursor`\nwith the same query and sort; do not construct an offset. Keep `match_types` and\n`article_entities` distinct from variant-literature match types. Report\n`semantic_index_used` and `semantic_degraded_reason`; a returned lexical match\ndoes not prove semantic retrieval worked. Preserve additional retrieval metadata\nreturned by the live service.\n\nDo not place patient information into a corpus query, even if the query is not\nvariant-specific.\n\n## Report a reproducible result\n\nInclude:\n\n1. The exact public query and `GRCh38` assembly.\n2. The returned status and, if resolved, the `canonical_key`.\n3. The structured evidence or literature result without changing its meaning.\n4. Source links and publication identifiers.\n5. Match type for literature results.\n6. Access date and any availability limitation.\n7. This boundary statement:\n\n> This is public, variant-level decision support for qualified professional\n> review. It does not evaluate patient, phenotype, family, segregation, or\n> private case data and is not a diagnosis or treatment recommendation.\n\n## Falsifiable smoke test\n\nUse the public rsID `rs80357914` to test ambiguity handling:\n\n```text\nCall search_variant_evidence with assembly GRCh38 and query rs80357914. If the\nresult is ambiguous, list the returned candidates and stop for explicit\nselection. Do not select a candidate or call downstream literature tools.\n```\n\nThe ambiguity branch passes only if an ambiguous response causes the workflow to\nstop without automatic candidate selection. If the live response changes, record\nthe actual status; a resolved response does not test ambiguity handling.\n\nOn 2026-09-30, live discovery reported adapter 1.5.0 and protocol 2026-07-28.\nThe rsID example returned `ambiguous`; a separate public HGVS query resolved and\nwas chained through its returned key to literature and a returned PMID. Corpus\ncursor pagination and gene-disease offset pagination were exercised. These are\ndated protocol checks, not validation of clinical accuracy. See the reference\nfor exact response shapes and source\u002Flive differences.\n\n## Official references\n\n- Integration setup: \u003Chttps:\u002F\u002Ffolklore.helena.bio\u002Fintegrations>\n- Technical guide: \u003Chttps:\u002F\u002Ffolklore.helena.bio\u002Fdocs\u002Ffolklore-connector>\n- Public adapter and contract: \u003Chttps:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp>\n- Official MCP Registry identity: `io.github.helena-bioinformatics\u002Ffolklore`\n",{"name":5,"license":15,"category":52,"metadata":53,"description":7,"compatibility":59},"scientific-computing",{"github":54,"version":55,"website":56,"skill-author":57,"last-reviewed":58},"https:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp","1.2","https:\u002F\u002Ffolklore.helena.bio","Helena Bioinformatics","2026-09-30","Requires network access to api.helena.bio (stateless Streamable HTTP MCP, no credentials) and a host supporting its advertised protocol, or curl for direct JSON-RPC POST requests.","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fkd-folklore-variant-evidence","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill folklore-variant-evidence",{"tool":75,"command":76},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill folklore-variant-evidence",{"tool":78,"command":79},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill folklore-variant-evidence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkd-folklore-variant-evidence\u002FSKILL.md",true,[83],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fmcp-contract.md","REFERENCE","参考文档",11040,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkd-folklore-variant-evidence\u002Freferences\u002Fmcp-contract.md",[90,119,144,169,194,218],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":99,"publishedAt":47},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,32,116,117,118],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","browsing","request","youtube transcripts",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":47},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[126,127,128,129,104,130,131,132,133,134,135,136,137,138,139,140,141,142,143,32],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","write","strategy","use","platform","grow","posting","competitive",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":47},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[150],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[152,137,153,154,155,156,157,158,139,159,160,60,161,162,163,164,165,166,167,168],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":47},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[176,177,178,179,180,181,182,183,184,139,185,111,186,187,188,189,190,191,192,193],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":47},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[200],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[202,203,204,205,206,154,181,207,208,209,210,211,137,212,110,213,214,215,216,217],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":224,"publishedAt":47},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[225,226,227,228,229,230,231,232,233,210,234,235,236,237,238,239,112,240,241,193],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]