CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ucsc-conservation-and-tfbs

Fetch Evolutionary Conservation scores (phyloP, phastCons) and Transcription Factor Binding Sites (TFBS) from the UCSC Genome Browser. Use when analyzing whether genomic variants or regions are evolutionarily conserved, functionally important, or bounded by TF regulators across major projects (ENCODE, JASPAR, ReMap).

Quality

88%

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

82%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 a strong, execution-focused reference: every workflow comes with a runnable command and realistic arguments, prerequisites include a conditional license-notification procedure, and anti-patterns add genuine expert judgment. Weaker spots are minor: some trimmed-able asides, no explicit output-error validation step, and an inlined track-version table plus an orphaned citation.bib that slightly blur the file structure.

Suggestions

Add a brief validation step after each query, e.g. 'Check the output JSON for an errorMessage field before parsing; UCSC returns 400 errors inline for invalid track names', which would close the workflow_clarity gap.

Move the hg38/hg19 collection/track tables (roughly lines 87-105) into a reference file (e.g. references/collections.md) and link to it, keeping the SKILL.md body as a lean overview.

Either reference references/citation.bib from the body (e.g., a one-line 'Cite as' note) or remove it from the bundle so every bundled file is discoverable from SKILL.md.

Trim explanatory asides like 'which is a strong signal for pathogenicity' that restate knowledge Claude already has.

DimensionReasoningScore

Conciseness

The body is operationally dense with little concept tutoring, but contains minor padding that could be trimmed, e.g. "which is a strong signal for pathogenicity" and "matching the UCSC Genome Browser's default comparative genomics tracks", and inlines version-bearing track lists (jaspar2024/jaspar2026) outside any deprecated/old-patterns section. Not 3 because there is no unnecessary explanation of basics; not 5 because every token does not quite earn its place.

4 / 5

Actionability

Every task section provides copy-paste-ready, fully executable commands with real coordinates, flags, and --output paths (e.g. "uv run scripts/get_conservation.py --coordinates \"chr1:215867804\" ... --output /tmp/cons_output.json"), covering the common cases: single bases, regions, collections, acceleration analysis, TFBS filtering, and track discovery. This matches the 5 anchor; a 4 would have minor gaps in coverage.

5 / 5

Workflow Clarity

Prerequisites are sequenced with explicit conditional logic (check for the license file, notify, then create it), each task maps to a single command, and the CAUTION note preempts a known 400 failure mode. Not 5 because there is no explicit post-query validation step (e.g., checking the output JSON for API errors before parsing); not 3 because sequence and most checkpoints are present and operations are read-only, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

The three utility scripts are clearly signaled with one-line purposes and are one level deep, and sections are well organized. Not 5 because the ~30-line hg38/hg19 collection tables are inlined rather than split into a reference file, and references/citation.bib exists in the bundle but is never referenced or navigable from the body — minor organization gaps matching the 4 anchor.

4 / 5

Total

17

/

20

Passed

Description

91%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 that clearly states what it does and when to use it, with concrete data types, the source system, and natural trigger phrases including synonyms and project names. The only weaknesses are secondary capabilities left unmentioned and slight overlap risk on the generic "functionally important" trigger.

DimensionReasoningScore

Specificity

"Fetch Evolutionary Conservation scores (phyloP, phastCons) and Transcription Factor Binding Sites (TFBS) from the UCSC Genome Browser" names the domain and several concrete actions with specific data types and source. It stops short of 5 because the skill also supports track listing, acceleration analysis, and lineage-specific collections, none of which are surfaced.

4 / 5

Completeness

It explicitly answers both questions: the "what" ("Fetch Evolutionary Conservation scores (phyloP, phastCons) and Transcription Factor Binding Sites (TFBS) from the UCSC Genome Browser") and a concrete "Use when" trigger clause ("analyzing whether genomic variants or regions are evolutionarily conserved, functionally important, or bounded by TF regulators"). This matches the 5 anchor; a 4 would have a less explicit or specific "when".

5 / 5

Trigger Term Quality

Natural terms a genomics user would actually say are comprehensively covered with synonyms: "evolutionarily conserved", "genomic variants", "Transcription Factor Binding Sites (TFBS)" (full term plus acronym), "UCSC Genome Browser", and project names "ENCODE, JASPAR, ReMap". Not 4 because no commonly used variant of these triggers is missing.

5 / 5

Distinctiveness Conflict Risk

The UCSC phyloP/phastCons/TFBS niche is mostly distinct with specific triggers, but "functionally important" variants could overlap with other variant-annotation or non-coding interpretation skills, which is minor overlap with closely related skills rather than the minimal conflict of the 5 anchor.

4 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

google-deepmind/science-skills

Path

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