folklore-variant-evidence

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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with clear branching workflows, validation checkpoints, and appropriate offloading of contract detail to one reference file. The main improvement is reducing repeated boundary statements and inlining a couple of tool-call examples.

Suggestions

Consolidate the repeated patient/phenotype/family/segregation prohibition into one canonical boundary section and reference it instead of restating it in 'Retrieve gene-disease assertions', the workflow, and the report sections.

Inline a minimal get_gene_disease_associations / search_literature_corpus call example (or a compact arguments block) rather than deferring solely to the reference.

Trim the repeated 'qualified professional review is required' phrasing to a single defined location (e.g. the report boundary statement) to save tokens.

Dimension	Reasoning	Score
Conciseness	Mostly lean and task-focused without explaining basics Claude already knows, but the patient/phenotype/family/segregation prohibition and the 'qualified professional review' boundary are restated several times across sections and could be tightened.	4 / 5
Actionability	Provides a copy-paste-ready curl call, exact tool arguments, and a concrete status-branching table; minor gaps remain where gene-disease and corpus calls defer to 'See the reference for request examples' instead of inlining the call.	4 / 5
Workflow Clarity	The variant-evidence workflow is a numbered three-step sequence with an explicit status-to-action table, validation checkpoints ('Only a resolved result may proceed automatically'), per-error feedback (stop, request corrected input), and a reproducible smoke test.	5 / 5
Progressive Disclosure	Well-organized sections with a single one-level-deep, clearly signaled reference (references/mcp-contract.md, verified to exist) holding the bulk contract detail while SKILL.md stays an overview plus workflow.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities and trigger conditions in third person with a sharp boundary. It could be made slightly more natural by adding lay synonyms alongside the technical outcome-state enumeration.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Retrieve ClinGen gene-disease validity assertions', 'review source-linked public evidence and literature', 'chain a resolved public variant into related literature or publication details', 'preserve evidence provenance' — with comprehensive coverage and no vague filler.	5 / 5
Completeness	Explicitly answers both 'what' (retrieve assertions, review evidence and literature) and 'when' via a concrete 'Use when a scientific agent must...' clause with multiple specific trigger conditions.	5 / 5
Trigger Term Quality	Good domain keyword coverage ('ClinGen gene-disease validity', 'GRCh38', 'germline nuclear SNV or simple indel', 'variant', 'literature'), but the trigger phrases lean technical (enumerating 'resolved, ambiguous, not-found, invalid, unsupported, or unavailable variant outcomes') rather than on natural user synonyms.	4 / 5
Distinctiveness Conflict Risk	Clear niche tied to a named MCP and ClinGen assertions, scoped to one variant type and an explicit no-patient-data boundary, making overlap with adjacent skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: K-Dense-AI/scientific-agent-skills
Path: skills/folklore-variant-evidence/SKILL.md
Commit: 49c6e97

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.