CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

alphagenome-variant-impact-score

Score, annotate, and analyze the functional impact of genetic variants using AlphaGenome Variant Impact (AVI) scores. Query variants in chr:pos:ref>alt format, annotate VCF/tabular callsets, perform saturation mutagenesis window scans (1-based closed chr:start-end), and extract GENCODE v46 GTF gene/exon/junction coordinates all via the AlphaGenome Atlas API.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/alphagenome_variant_impact_score/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 content is exceptionally actionable, with verified executable commands, concrete output schemas, and precise operational sizing/timing guidance throughout. Its weaknesses are the absence of explicit validation or verification steps for batch operations (which caps workflow clarity) and reference material inlined in SKILL.md that could be split out. Adding post-batch output verification would address the lowest-scoring dimension.

Suggestions

Add explicit verification steps after batch 'annotate' runs, e.g., compare the output record count against the input callset, confirm the output file is non-empty, and check stdout summary counts before reporting results.

Add an error-recovery loop for long-running operations (e.g., what to do if a >=10,000-variant run is interrupted or the GTF download stalls past the 60-90 s window).

Move the detailed output field schemas ('Output Schemas & Response Structures') and the Phred threshold table into a references/ file, keeping SKILL.md as a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body is densely operational — commands, output sizes, runtimes, and schemas — and assumes genomics knowledge instead of re-explaining it, but includes trimmable internal details ('~4.37 GB RAM', 'corp/Cloudtop networks' timing) and repeated per-command output-size warnings. Efficient with minor instances that could be trimmed, fitting the 4 anchor rather than the every-token-earns-its-place level of 5.

4 / 5

Actionability

Every section provides copy-paste-ready 'uv run scripts/alphagenome_atlas_avi.py ...' commands with real flags (-o, --format json, --top_k, --include_track_info), all five subcommands verified present in the bundled script, plus a complete executable Python SDK example covering the 0-based/1-based coordinate conversion. Specific examples cover the common cases for each command.

5 / 5

Workflow Clarity

The five CLI workflows are clearly sequenced with operational guardrails ('always export directly to a file', 'Do not kill the process prematurely during initial download'), but batch operations such as 'annotate' on >=500-variant callsets have no explicit output verification or error-recovery steps. Per the judging guidelines, a batch workflow without validation is capped at 3, so the 4 anchor ('most checkpoints present') does not apply.

3 / 5

Progressive Disclosure

A well-sectioned overview with a clear, verified reference to the bundled 'scripts/alphagenome_atlas_avi.py' and organized command/schema/interpretation sections. Minor gaps: the ~80-line output-schema and score-interpretation detail could move to a references/ file, and 'scripts/alphagenome_atlas_links.py' points into another skill's bundle rather than this one — good structure with minor organization gaps, the 4 anchor.

4 / 5

Total

16

/

20

Passed

Description

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

The description is highly specific and action-dense, clearly conveying what the skill does with concrete formats and operations. Its main weakness is the complete absence of 'when to use' trigger guidance, which caps completeness, and slightly jargon-heavy trigger vocabulary. Adding an explicit 'Use when...' clause would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g.: 'Use when scoring or prioritizing genetic variants, annotating VCFs with functional impact predictions, or running saturation mutagenesis scans of a genomic window.'

Include common user synonyms and file extensions such as 'variant effect', 'variant prioritization', 'SNV', and '.vcf' alongside the existing technical terms.

Trim internal jargon in the first sentence (e.g., lead with 'genetic variant impact scores' before introducing the AVI abbreviation) so the opening matches how users phrase requests.

DimensionReasoningScore

Specificity

Lists five distinct concrete actions with format-level detail: 'Score, annotate, and analyze the functional impact of genetic variants', 'Query variants in chr:pos:ref>alt format', 'annotate VCF/tabular callsets', 'perform saturation mutagenesis window scans', and 'extract GENCODE v46 GTF gene/exon/junction coordinates'. Coverage is comprehensive with no gaps, matching the top anchor rather than the 'minor gaps' level below it.

5 / 5

Completeness

The 'what' is clearly and comprehensively answered, but the description contains no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because that level requires both 'what' and an explicit (if imperfect) 'when'.

3 / 5

Trigger Term Quality

Includes good natural terms ('genetic variants', 'functional impact', 'VCF', 'annotate', 'saturation mutagenesis') but leans technical (AVI, GENCODE v46, Atlas API) and misses common variations such as 'variant effect', 'variant prioritization', or the '.vcf' extension. Good coverage with a few natural terms missing — fits the 4 anchor, not the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

Names a specific platform ('AlphaGenome Variant Impact (AVI)', 'AlphaGenome Atlas API') establishing a clear niche, but generic phrasing like 'annotate VCF/tabular callsets' creates minor overlap risk with closely related variant-annotation skills. Mostly distinct with minor overlap — the 4 anchor — rather than the minimal conflict risk required for 5.

4 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/alphagenome_atlas_links.py)

Warning

Total

14

/

16

Passed

Repository

google-deepmind/science-skills

Path

skills/alphagenome_variant_impact_score/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.