Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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).
.claude/skills/mkurman-ucsc-conservation-and-tfbs/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | 84% | 0% |
| case-11 | ✓→✗ | ▼ Worse | 181% | 0% |
| case-19 | ✓→✗ | ▼ Worse | -6% | 0% |
| case-20 | ✓→✗ | ▼ Worse | 30% | 0% |
| case-15 | ✓→✓ | = Same ✓ | 39% | 0% |
This skill provides access to evolutionary constraint scores and conserved elements from the UCSC Genome Browser. It retrieves scores from the PHAST package — specifically phastCons (identifying functional blocks) and phyloP (measuring individual site constraint) — calculated from multiple alignments.
Use this skill to determine if a non-coding variant hits a site that hasn't changed since a common ancestor (which is a strong signal for pathogenicity) or to find conservation peaks across a regulatory element.
uv: Read the uv skill and follow its Setup instructions to ensureuv is installed and on PATH.
this skill directory then (1) prominently notify the user to check the terms at https://genome.ucsc.edu/conditions.html and https://genome.ucsc.edu/goldenPath/help/api.html, then (2) create the file recording the notification text and timestamp.
database rather than accessing the database directly. The scripts automatically enforce the required rate limit gracefully.
file. Parse it separately (using jq or your own code).
output.
This skill includes scripts to query different types of genomic data from UCSC:
scripts/get_conservation.py: For Evolutionary Conservation scores(phyloP, phastCons).
scripts/get_tfbs.py: For Transcription Factor Binding Sites (TFBS).scripts/list_tracks.py: For listing available tracks based on searchor group constraints.
Always use the hg38 genome assembly by default, unless the user has specified otherwise.
To get the evolutionary constraint at a single base, or a list of specific bases. This is optimal for single nucleotide variants (SNVs). phyloP is the best metric for individual bases.
bashuv run scripts/get_conservation.py --coordinates "chr1:215867804" "chr1:215867823" --output /tmp/cons_output.json
To identify "conservation peaks" across a non-coding regulatory element (like an enhancer) to see if an ISM-predicted importance peak aligns with evolutionary history. phastCons is best for functional windows due to HMM smoothing. The --conserved-elements flag will also retrieve predefined blocks under extreme constraint.
bashuv run scripts/get_conservation.py --coordinates "chr8:11748914-11749085" --conserved-elements --output /tmp/region_cons.json
You can control the evolutionary depth using the --collection flag. The default (vertebrate) uses the 100-vertebrate Multiz alignment for both hg38 and hg19, matching the UCSC Genome Browser's default comparative genomics tracks.
vertebrate (default): UCSC 100-vertebrate Multiz alignment. phyloP:phyloP100way, phastCons: phastCons100way.
mammal: Hiller Lab 470-way mammalian alignment. phyloP:phyloP470wayBW, phastCons: phastCons470way.
primate: UCSC 30-primate Multiz alignment. phyloP: phyloP30way,phastCons: phastCons30way.
vertebrate (default): UCSC 100-vertebrate Multiz alignment. phyloP:phyloP100way, phastCons: phastCons100way.
vertebrate46: UCSC 46-vertebrate Multiz alignment (legacy). phyloP:phyloP46wayAll, phastCons: phastCons46way.
mammal: 46-way placental mammal subset. phyloP:phyloP46wayPlacental, phastCons: phastCons46wayPlacental.
primate: 46-way primate subset. phyloP: phyloP46wayPrimates,phastCons: phastCons46wayPrimates.
bash# hg38 mammal (Hiller 470-way) uv run scripts/get_conservation.py --coordinates "chr5:1045330-1046172" --collection mammal --output /tmp/mammal_cons.json # hg19 with legacy 46-vertebrate alignment uv run scripts/get_conservation.py --coordinates "chr5:1045330-1046172" --genome hg19 --collection vertebrate46 --output /tmp/vert46_cons.json
To analyze whether a specific locus is undergoing evolutionary acceleration (i.e. evolving more rapidly than the neutral drift baseline), use --analyze. This will compute scalar statistics (mean, min, max) for phyloP scores and provide a heuristic boolean is_accelerated to simplify your evaluation.
bashuv run scripts/get_conservation.py --coordinates "chr5:1045330-1046172" --analyze --output /tmp/accelerated_cons.json
To identify transcription factor binding sites for a given genomic interval. This is useful for interpreting non-coding variants that might disrupt TF binding.
Run scripts/get_tfbs.py with --coordinates and --tracks. You can query multiple tracks at once.
bashuv run scripts/get_tfbs.py --coordinates "chr11:1001000-1010000" --tracks encRegTfbsClustered --output /tmp/tfbs_encode.json
JASPAR tracks may return very large result sets. Use --tf-filter to keep only items whose TFName field contains the given substring (case-insensitive):
bashuv run scripts/get_tfbs.py --coordinates "chr6:36670000-36690000" --tracks jaspar2024 --tf-filter TP53 --output /tmp/tp53_sites.json
encRegTfbsClustered (TF Clusters)jaspar2026, jaspar2024 (Predicted TFBS)ReMapTFs (ChIP-seq Atlas)> !CAUTION] Tracks like jaspar or ReMap without years are often "container" > tracks and will fail with a 400 error. Always use the specific subtrack name > (e.g., jaspar2026).
To list available tracks (such as different versions of JASPAR, or purely to discover what tracks exist for a particular genome assembly):
bashuv run scripts/list_tracks.py --search "jaspar" --output /tmp/jaspar_tracks.json
You can also filter by functional group:
bashuv run scripts/list_tracks.py --group "regulation" --output /tmp/regulation_tracks.json
--collection mammal) constraint if you areexplicitly looking for deep evolutionary roots across all vertebrates. Use the default vertebrate collection.
of a nucleotide (this skill provides measures of how much sites have changed, not what the ancestral nucleotide was).
it could also reflect a high local mutation rate which conservation scores alone cannot distinguish.
output is too large. Use jq or write your own code to parse the output files.
should be to always use hg38.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-11 | pass→fail | 10,408 | 9,513 | -9% | 1 | 1 | 0% | 868 | 2,435 | +181% | 0 | 0 | — |
case-12 | fail→fail | 9,034 | 6,181 | -32% | 1 | 1 | 0% | 506 | 2,342 | +363% | 0 | 0 | — |
case-13 | fail→fail | 6,301 | 8,024 | +27% | 1 | 1 | 0% | 281 | 2,613 | +830% | 0 | 0 | — |
case-04 | fail→fail | 9,213 | 6,865 | -25% | 1 | 1 | 0% | 581 | 2,358 | +306% | 0 | 0 | — |
case-05 | fail→pass | 10,464 | 15,276 | +46% | 1 | 1 | 0% | 1,984 | 3,653 | +84% | 0 | 0 | — |
case-01 | fail→fail | 9,602 | 7,481 | -22% | 1 | 1 | 0% | 351 | 2,369 | +575% | 0 | 0 | — |
case-02 | fail→fail | 9,754 | 7,754 | -21% | 1 | 1 | 0% | 554 | 2,516 | +354% | 0 | 0 | — |
case-03 | fail→fail | 6,936 | 8,879 | +28% | 1 | 1 | 0% | 406 | 2,668 | +557% | 0 | 0 | — |
case-06 | fail→fail | 18,725 | 6,539 | -65% | 1 | 1 | 0% | 2,333 | 2,497 | +7% | 0 | 0 | — |
case-07 | fail→fail | 7,637 | 5,925 | -22% | 1 | 1 | 0% | 396 | 2,331 | +489% | 0 | 0 | — |
case-08 | fail→fail | 18,721 | 8,435 | -55% | 1 | 1 | 0% | 3,432 | 2,826 | -18% | 0 | 0 | — |
case-09 | fail→fail | 9,235 | 20,931 | +127% | 1 | 1 | 0% | 429 | 2,323 | +441% | 0 | 0 | — |
case-10 | fail→fail | 9,173 | 5,626 | -39% | 1 | 1 | 0% | 1,893 | 2,273 | +20% | 0 | 0 | — |
case-14 | fail→fail | 10,878 | 10,703 | -2% | 1 | 1 | 0% | 1,848 | 2,778 | +50% | 0 | 0 | — |
case-15 | pass→pass | 12,469 | 3,052 | -76% | 1 | 1 | 0% | 1,865 | 2,594 | +39% | 0 | 0 | — |
case-16 | pass→pass | 10,505 | 8,458 | -19% | 1 | 1 | 0% | 1,796 | 2,809 | +56% | 0 | 0 | — |
case-17 | fail→fail | 20,073 | 6,197 | -69% | 1 | 1 | 0% | 2,163 | 2,314 | +7% | 0 | 0 | — |
case-18 | fail→fail | 17,826 | 10,024 | -44% | 1 | 1 | 0% | 3,614 | 2,416 | -33% | 0 | 0 | — |
case-19 | pass→fail | 15,421 | 7,513 | -51% | 1 | 1 | 0% | 2,559 | 2,405 | -6% | 0 | 0 | — |
case-20 | pass→fail | 12,814 | 9,826 | -23% | 1 | 1 | 0% | 1,996 | 2,602 | +30% | 0 | 0 | — |
case-21 | fail→fail | 14,028 | 13,499 | -4% | 1 | 1 | 0% | 2,442 | 4,345 | +78% | 0 | 0 | — |
case-22 | fail→fail | 12,149 | 9,103 | -25% | 1 | 1 | 0% | 2,022 | 2,596 | +28% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 5 counted toward the lift figure. The other 17 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of -9 percentage points is the difference between those two pass rates over the 5 comparable cases. 8 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.