[{"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",1559,"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",474,"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-11 14:40:14",{"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,109,116,142,166],{"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":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":101},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":97,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":101},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":101},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":48},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[123,124,125,126,127,128,129,130,131,132,133,31,134,135,136,137,138,139,140,141],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":48},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[149,150,47,137,151,152,153,154,155,156,157,158,159,160,128,161,162,163,164,165],"deja reflect","reflect","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":179,"publishedAt":48},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[172,175,176],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[168,180,181,182,183,184,185,162,186,129,187,188,39,189,31,190,191,192,44,193],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","song","image","mcp server","schedule","publish"]