CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

alphagenome-single-variant-analysis

Analyzes genetic variant effects on gene expression (RNA-seq), chromatin accessibility (DNASE), histone marks (ChIP), and transcription factors using the AlphaGenome API. Use when the user asks about non-coding variant effects, pathogenicity, clinical significance, disease associations, functional effects, gene expression changes, splicing disruption, or regulatory effects in promoters and enhancers. Also use for resolving biological terms to tissue/cell-type ontologies (UBERON/CL) or analyzing variants in chr:pos:ref>alt format.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is an efficient, highly actionable operator's manual for a complex API, with executable code, hard-won gotchas, and a sequenced checklist with a self-critique step. Its main weakness is bundle integrity: the docs/ files it declares MANDATORY (interpretation guide, report templates, examples) do not exist in the bundle, undermining both navigation and workflow completeness.

Suggestions

Fix reference integrity: either add the missing docs/ files (alphagenome-api.md, interpretation-guide.md, report-templates.md, examples/*) to the bundle or repoint the References section to wherever they actually live, since steps 5 and 6 of the workflow are MANDATORY reads of these files.

Consolidate the uv usage rule into one section (it currently appears in Prerequisites, Core Rules, and Environment Setup) and move the Splicing Zoom Strategy detail out of the References list into the referenced script's documentation.

Add a short executable snippet or command line for the visualization step (Step 4) — e.g., the actual `uv run scripts/visualize_variant_effects.py ...` invocation — so the checklist steps don't depend solely on the missing docs.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, hard-won operational knowledge ("Convert boolean masks to integer indices using np.flatnonzero(mask)", GTF column capitalization, "score_variant does NOT accept ontology_terms"), which Claude could not know. Not 5 because the `uv run` rule is repeated in Prerequisites, Core Rules, and Environment Setup, and the nested "Splicing Zoom Strategy" bullets under References restate detail that belongs with the referenced script.

4 / 5

Actionability

The Broad Discovery Scan is a complete, copy-paste-ready executable block (dotenv loading, client creation, scorer filtering, tidy/rank/print), and troubleshooting items give concrete fixes (e.g., "set UV_INDEX_URL=https://pypi.org/simple"). Not 5 because the Extended Search snippet is a fragment assuming prior state, and the visualization and multi-variant "spawn sub-agents" steps lack any inline executable guidance — they rely entirely on referenced materials, two of which are absent from the bundle.

4 / 5

Workflow Clarity

An explicit 8-step sequenced checklist with MANDATORY markers and a genuine validation checkpoint ("Step 7: Self-Critique (view report.md to verify links & claims)"), plus an error-recovery-oriented troubleshooting section. Not 5 because most steps are one-line labels whose mechanics live in referenced docs, and the two MANDATORY documents the workflow depends on (interpretation-guide.md, report-templates.md) are not present in the bundle, leaving steps 5 and 6 underspecified. Not 3 because the sequence and at least one explicit feedback loop are present and this is not a destructive/batch operation requiring stronger validation.

4 / 5

Progressive Disclosure

The References section is well-signaled with one-paragraph descriptions per entry and scripts referenced by relative path that do exist (scripts/lookup_gene_info.py, scripts/visualize_variant_effects.py, etc.). However, scored against the actual bundle: every docs/ path — docs/alphagenome-api.md, docs/interpretation-guide.md, docs/report-templates.md, and all docs/examples/* — is absent (the bundle contains only references/citation.bib and scripts/), so the MANDATORY interpretation guide and report templates are dead links and navigation breaks for the most critical materials. Not 4 because this is more than a minor organization gap; not 2 because the structure and signaling that exist are good and the scripts resolve correctly.

3 / 5

Total

15

/

20

Passed

Description

95%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 description in third-person voice that clearly states capabilities and provides an explicit, comprehensive "Use when" clause with natural domain trigger phrases. Only minor room to grow by enumerating secondary capabilities like visualization or in-silico mutagenesis.

DimensionReasoningScore

Specificity

Concrete actions are named across multiple assay types — "Analyzes genetic variant effects on gene expression (RNA-seq), chromatin accessibility (DNASE), histone marks (ChIP), and transcription factors" — plus "resolving biological terms to tissue/cell-type ontologies (UBERON/CL)" and "analyzing variants in chr:pos:ref>alt format". Falls just short of the 5 anchor because the dominant verb is a single "Analyzes" applied to several objects, and capabilities covered in the body (visualization, ISM, report generation) are omitted.

4 / 5

Completeness

Explicitly answers both: "what" ("Analyzes genetic variant effects on gene expression... using the AlphaGenome API") and "when" ("Use when the user asks about non-coding variant effects, pathogenicity..." plus "Also use for resolving biological terms..."). Matches the anchor-5 example pattern of concrete capability statement followed by explicit trigger clause; not 4 because the 'when' is already fully explicit with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases: "non-coding variant effects", "pathogenicity", "clinical significance", "disease associations", "functional effects", "gene expression changes", "splicing disruption", "regulatory effects in promoters and enhancers", plus the concrete "chr:pos:ref>alt format" a user would paste. These are exactly the words a genomics user would say; not the level below (4) because no commonly used domain phrasing is obviously missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (AlphaGenome API variant-effect analysis, ontology resolution, chr:pos:ref>alt parsing) with distinct domain-specific triggers; minimal realistic overlap with other skills. Third-person voice is used correctly ("Analyzes", not "I can"/"You can").

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 9 possibly missing (docs/alphagenome-api.md, docs/examples/model_limitation_RNU4ATAC/, docs/examples/negative_result_GATA4/, docs/examples/negative_result_TGFB3/, docs/examples/polyadenylation_HBA2/, +4 more), 6 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

google-deepmind/science-skills

Path

skills/alphagenome_single_variant_analysis/SKILL.md

Reviewed

Table of Contents

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.