gtex-database

Use when you want to retrieve quantitative RNA expression data and variant eQTL information from the GTEx (Genotype-Tissue Expression) Project across 54 non-diseased tissue sites.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/gtex_database/SKILL.md

Quality

Content

80%Weight 40%Scale 1-3

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

The body is lean and highly actionable with executable examples for every command. Its main weaknesses are a workflow that leaves a placeholder unfilled and lacks validation checkpoints, and an orphaned reference file with no in-body navigation.

Suggestions

Replace the '<gencode_id>' placeholder in Typical Workflows step 2 with the actual resolved value and add an explicit validation checkpoint (e.g., verify the JSON from step 1 contains the GENCODE ID before running step 2).

Reference references/citation.bib from the body (e.g., a 'Citation' section linking to it) so the bundled reference file is discoverable and not orphaned.

Deduplicate the resolve-gencode-id example that appears in both Quick Start and section 1, and tighten the overlap between the 'When to Use' bullets and the 'Command Selection Guide' to further improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with only minimal expansions (TPM, eQTL) that aid correct command use; minor cross-referenced repetition between Quick Start and the Commands section is light rather than padded.	3 / 3
Actionability	Every subcommand ships fully executable 'uv run scripts/gtex_cli.py ...' examples with concrete positional and optional arguments plus defaults, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	Typical Workflows provides a clear two-step sequence, but step 2 uses a placeholder '<gencode_id>' instead of the resolved value and there are no explicit validation or error-recovery checkpoints, matching the 'steps listed but validation gaps' anchor.	2 / 3
Progressive Disclosure	Sections are well organized, but the bundle's references/citation.bib is never referenced or signaled from the body and there are no one-level-deep detail files to navigate to, matching the 'some structure but references not clearly signaled' anchor.	2 / 3
	Total	10 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 clearly defines a distinctive niche and answers both what and when with an explicit trigger. It is slightly held back by relying on a single verb and formal phrasing rather than broader natural trigger variations.

Dimension	Reasoning	Score
Specificity	Names the concrete domain (GTEx, 54 non-diseased tissues) and the action 'retrieve quantitative RNA expression data and variant eQTL information', but relies on a single verb covering two data types rather than enumerating multiple distinct actions like the score-3 anchor.	2 / 3
Completeness	Explicitly states both what it does ('retrieve quantitative RNA expression data and variant eQTL information from the GTEx... Project') and when to use it ('Use when you want to...'), satisfying the score-3 anchor with an explicit trigger.	3 / 3
Trigger Term Quality	Includes relevant specialist keywords ('RNA expression', 'eQTL', 'GTEx') but the phrasing 'Use when you want to retrieve' is somewhat formal and lacks common lay variations, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The GTEx / eQTL / 54 non-diseased tissue niche is highly specific with distinct triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 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: google-deepmind/science-skills
Path: skills/gtex_database/SKILL.md
Commit: 0b42509

Reviewed: 8 days 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.