CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gget

Queries 20+ bioinformatics resources through CLI/Python. Supports quick lookups of gene info, BLAST/BLAT, viral sequence downloads, PDB/mmCIF structures, G2P residue annotations, enrichment analysis, OpenTargets, COSMIC, CELLxGENE, and 8cube mouse specificity/expression data. Best for interactive exploration and simple queries. For batch processing or advanced BLAST use biopython; for multi-database Python workflows use bioservices.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, information-dense skill body: executable install and script commands, honest verification boundaries, and clean one-level-deep splitting of catalogs, workflows, and service contracts across reference files. It stops short of top marks on in-body example queries, inline workflow sequences, and a fully complete Resources listing.

Suggestions

Add one or two in-body example queries for the most common cases (e.g., `gget info ENSG00000141510` and a Python `gget.seq(...)` call) so the SKILL.md itself demonstrates a round-trip without requiring a hop to module_catalog.md.

Make the "### references/" Resources section list all five reference files, including module_catalog.md and common_workflows.md, so navigation does not depend on links embedded in body prose.

Tighten the longest best-practices bullets (Enrichr, Census) by moving parameter-level caveats into references/database_info.md and keeping only the actionable rule in the body.

DimensionReasoningScore

Conciseness

The body is dense with tool-specific facts Claude would not know (e.g., "Census `meta_only=True` returns cells, not datasets, and ignores the gene filter"; "Open Targets filters are local and applied after `limit`") with no padding of generic concepts. A few spots could be trimmed: the multi-line Enrichr best-practices bullet and the lengthy arXiv citation-fetching instructions. This fits "efficient; minor instances of over-explanation that could be trimmed" rather than the 5 anchor where every token earns its place.

4 / 5

Actionability

Concrete, copy-paste-ready guidance is given: the install block (`uv venv --python 3.13 .venv` / `uv pip install "gget==0.30.8"`), exact script invocations ("`scripts/gene_analysis.py TP53`", "`scripts/enrichment_pipeline.py genes.txt --background tested_genes.txt`"), and specific calls like `gget.pdb(..., resource="mmcif")` and `gget setup <module>`. The gap versus the 5 anchor: the body itself contains no example query invocation for the most common case (e.g., a `gget info`/`gget seq` call); those examples are deferred to references/module_catalog.md.

4 / 5

Workflow Clarity

Multi-step workflows are delegated to references/common_workflows.md, whose table pairs each task with an explicit checkpoint column ("Preserve Ensembl index; inspect service failures; distinguish genomic sequence from CDS"; "checksums -> downstream index"), and the Error Handling section gives a recovery pattern ("check upstream release notes and pin the newer fixed version explicitly") plus batch limits ("Process max ~1000 Ensembl IDs at once"). Not the 5 anchor because the feedback loops and full sequences live one file away rather than in the body, and a couple of workflows are summarized only as table rows. Validation for batch/paginated operations is present, so the destructive/batch cap is not triggered.

4 / 5

Progressive Disclosure

The body is a genuine overview: per-parameter detail split into module_catalog.md and module_reference.md, workflows into common_workflows.md and workflows.md, service contracts into database_info.md — all one level deep, all markdown-linked, and all five referenced files verified to exist on disk. The structure sits between the 4 and 5 anchors because the "### references/" Resources section lists only three of the five files (omitting module_catalog.md and common_workflows.md, which are linked earlier in the body), a minor navigation gap against the "easy navigation" 5 anchor.

4 / 5

Total

16

/

20

Passed

Description

83%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, third-person description that states concrete capabilities comprehensively and explicitly disambiguates against neighboring tools. The 'when' guidance is present but phrased somewhat abstractly ("interactive exploration and simple queries"), and a few natural trigger synonyms (sequence alignment, orthology, single-cell) are absent.

Suggestions

Replace or augment "Best for interactive exploration and simple queries" with concrete trigger phrases, e.g. "Use when looking up a gene's info or sequence, running a quick BLAST, or fetching protein structures and viral sequences."

Add user-facing synonyms alongside the database brand names, e.g. "sequence alignment", "orthology", "single-cell expression", so the description triggers on natural phrasing rather than only tool-specific jargon.

DimensionReasoningScore

Specificity

"quick lookups of gene info, BLAST/BLAT, viral sequence downloads, PDB/mmCIF structures, G2P residue annotations, enrichment analysis, OpenTargets, COSMIC, CELLxGENE, and 8cube mouse specificity/expression data" lists multiple concrete capabilities with near-complete coverage of the tool's scope, plus explicit boundary actions (biopython/bioservices redirects). This matches the anchor for multiple specific concrete actions with comprehensive coverage; it is not the level below, which requires minor gaps in coverage.

5 / 5

Completeness

The 'what' is explicit ("Queries 20+ bioinformatics resources through CLI/Python" plus the capability list), and a 'when' clause exists via "Best for interactive exploration and simple queries" reinforced by negative triggers ("For batch processing or advanced BLAST use biopython"). However, "interactive exploration and simple queries" is more abstract than concrete trigger phrases, so the 'when' could be more explicit and specific — the 4 anchor rather than the 5 anchor which demands concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural phrases users would say are present ("gene info", "BLAST", "viral sequence downloads", "PDB/mmCIF structures", "enrichment analysis", "expression data"), but coverage is not comprehensive: database brand names ("G2P", "8cube", "CELLxGENE") are jargon rather than user-said phrases, and common synonyms such as "sequence alignment", "orthology", or "single-cell" are missing. Good coverage with a few natural terms missing fits the 4 anchor, not the 5 anchor requiring synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (gget CLI/Python for unified querying of genomics databases) and actively reduces conflict risk by redirecting adjacent needs to named alternatives: "For batch processing or advanced BLAST use biopython; for multi-database Python workflows use bioservices." This matches the clear-niche, minimal-conflict-risk anchor; it is not the level below, which would leave overlap with closely related skills unaddressed.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

K-Dense-AI/scientific-agent-skills

Path

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