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

Passed

No findings from the security scan

The canonical home for this skill is folklore-variant-evidence in K-Dense-AI/scientific-agent-skills

Quality

Content

92%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, highly actionable skill body with clear sequencing, explicit validation via status branching, and clean one-level-deep reference usage. The only weakness is repetition of the patient-data boundary statement across multiple sections.

Suggestions

Consolidate the repeated patient/phenotype/family/segregation boundary into one canonical statement in 'Enforce the input boundary' and reference it from later sections rather than restating it verbatim each time.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of generic-concept padding, but the no-patient/phenotype/family/segregation boundary is restated in several sections and the report boundary statement, which could be trimmed to a single canonical statement cross-referenced where needed.	4 / 5
Actionability	Provides a fully executable copy-paste curl JSON-RPC call, concrete tool names with parameter shapes, a status-to-action table, and request examples in the referenced contract — covering the common cases directly.	5 / 5
Workflow Clarity	The variant-evidence workflow is explicitly sequenced (resolve → branch on status → review without overclaiming) with the status table acting as validation checkpoints and an explicit stop rule for ambiguous results.	5 / 5
Progressive Disclosure	SKILL.md reads as a well-organized overview with a single clearly signaled one-level-deep reference (references/mcp-contract.md, verified present) for the detailed contract; navigation is easy and content is appropriately split.	5 / 5
	Total	19 / 20 Passed

Description

85%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 with clear what/when structure and a distinct niche, weakened only by jargon-heavy trigger phrasing that is less natural for end-user invocation. Scope boundaries are unusually well articulated.

Suggestions

Soften the trigger clause toward natural user phrasing (e.g., 'Use when looking up ClinGen gene-disease validity or public variant evidence and linked literature for a single GRCh38 variant') rather than agent-control-flow language.

Add a few common synonyms lay users might say (e.g., 'pathogenicity', 'variant interpretation', 'rsID lookup') alongside the existing technical terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Retrieve ClinGen gene-disease validity assertions', 'review source-linked public evidence and literature for one supported GRCh38 germline nuclear SNV or simple indel', 'chain a resolved public variant into related literature or publication details' — covering the capability comprehensively.	5 / 5
Completeness	Explicitly states both what ('Retrieve ClinGen gene-disease validity assertions... review source-linked public evidence and literature...') and when via a concrete 'Use when...' clause enumerating trigger scenarios.	5 / 5
Trigger Term Quality	Relevant keywords appear (ClinGen, gene-disease, variant, evidence, literature, publication), but the trigger framing leans technical ('a scientific agent must branch deterministically on resolved, ambiguous, not-found...') rather than natural user phrasing, and common synonyms are partial.	3 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — Folklore Clinical Variant Interpretation MCP, one public GRCh38 germline SNV/indel, ClinGen validity — with distinct triggers and explicit scope exclusions (no patient data), minimizing overlap with adjacent skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: synthetic-sciences/openscience
Path: backend/cli/skills/biology/folklore-variant-evidence/SKILL.md
Commit: 4e060d6

Reviewed: 7 hours 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.