[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MA4FSMWKFFSBD9CCH6TJC4":3,"skill-same:01M6MA4FSMWKFFSBD9CCH6TJC4":92},{"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":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6MA4FSMWKFFSBD9CCH6TJC4","folklore-variant-evidence",null,"Retrieve ClinGen gene-disease validity assertions for a public gene or disease, and review source-linked public evidence and literature for one supported GRCh38 germline nuclear SNV or simple indel through Folklore Clinical Variant Interpretation MCP. Use 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.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ffolklore-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,47],"variant","folklore variant evidence","evidence","patient","when","variants","literature","indel","snv","chain","host","invalid","MCP","clinical","genetics","branch","access","api","credentials","interpretation","review","2026-11-10 10:12:30",false,"---\nname: folklore-variant-evidence\ndescription: Retrieve ClinGen gene-disease validity assertions for a public gene or disease, and review source-linked public evidence and literature for one supported GRCh38 germline nuclear SNV or simple indel through Folklore Clinical Variant Interpretation MCP. Use 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); works from any MCP-capable host or via JSON-RPC POST with curl.\nmetadata:\n  version: '1.0'\n  category: life-sciences\n  maintainer: Kalaris Labs\n  website: https:\u002F\u002Ffolklore.helena.bio\n  github: https:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp\n  contributor: Helena Bioinformatics\n  tags: clinical genomics, variant interpretation, ClinGen, germline variants, genetics\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\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 indel.\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 URL, date and snapshot. Do not combine distinct diseases or silently choose among name matches. Gene-disease validity does not classify a particular variant. Empty results mean no matching assertion in the available ClinGen source, not no association. No patient, phenotype, family, segregation, private case data or sequencing files may 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\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. If a resolved interpretation itself reports unavailable\nevidence, preserve that separate limitation.\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- 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\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 test passes only if an ambiguous response causes the workflow to stop\nwithout automatic candidate selection.\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\n## Related skills\n\n- `bgpt-paper-search`: Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server.\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\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 indel.\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 URL, date and snapshot. Do not combine distinct diseases or silently choose among name matches. Gene-disease validity does not classify a particular variant. Empty results mean no matching assertion in the available ClinGen source, not no association. No patient, phenotype, family, segregation, private case data or sequencing files may 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\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. If a resolved interpretation itself reports unavailable\nevidence, preserve that separate limitation.\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- 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\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 test passes only if an ambiguous response causes the workflow to stop\nwithout automatic candidate selection.\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\n## Related skills\n\n- `bgpt-paper-search`: Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server.\n",{"name":5,"license":15,"metadata":53,"description":7,"compatibility":61},{"tags":54,"github":55,"version":56,"website":57,"category":58,"maintainer":59,"contributor":60},"clinical genomics, variant interpretation, ClinGen, germline variants, genetics","https:\u002F\u002Fgithub.com\u002Fhelena-bioinformatics\u002Ffolklore-mcp","1.0","https:\u002F\u002Ffolklore.helena.bio","life-sciences","Kalaris Labs","Helena Bioinformatics","Requires network access to api.helena.bio (stateless Streamable HTTP MCP, no credentials); works from any MCP-capable host or via JSON-RPC POST with curl.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ffolklore-variant-evidence",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill folklore-variant-evidence",{"tool":78,"command":79},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill folklore-variant-evidence",{"tool":81,"command":82},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill folklore-variant-evidence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ffolklore-variant-evidence\u002FSKILL.md",true,[86],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fmcp-contract.md","REFERENCE","参考文档",3545,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ffolklore-variant-evidence\u002Freferences\u002Fmcp-contract.md",[93,102,110,118,126,134],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":101},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":101},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":101},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":101},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":101},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":101},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]