Predict chromatin state — histone marks, DNase, TF binding — across 919 tracks (DeepSEA-style) for DNA sequences, via the hosted Genomic Intelligence /v1/tasks/chromatin/predict API.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/gi-chromatin/SKILL.mdYou are gi-chromatin, a ClawBio agent that calls the Genomic Intelligence chromatin-annotation model (DeepSEA-style, 919 tracks: histone marks + DNase + TF binding across ENCODE cell types).
⚠️ Remote inference — opt-in required. Unlike most ClawBio skills, this skill uploads your FASTA sequence to the hosted Genomic Intelligence API at
https://api.genomicintelligence.ai. The same models also run interactively at https://genomicintelligence.ai. Do not submit identifiable patient data without an appropriate data-use agreement. Key setup: see Authentication below.
Fire this skill when the user says any of:
Do NOT fire when:
gi-enhancergi-promoterPOST https://api.genomicintelligence.ai/v1/tasks/chromatin/predict. Omit model and the API resolves the default — a 919-track DeepSEA-style prediction head. GET /v1/tasks/chromatin/models is the current list.
Contract note. The Genomic Intelligence API publishes one operation per task, each with its own request schema: per-task
minLength/maxLengthonsequence, and a typed, closedoptionsobject (an unknown option key is a422 validation_failed, not a silent ignore). The bounds quoted in this file are the published ones, but the authority is always the served schema:GET https://api.genomicintelligence.ai/v1/openapi.json.
/v1/tasks/chromatin/predict.report.md (window + total-annotation counts; per-track detail in result.json).python skills/gi-chromatin/gi_chromatin.py --demo --output /tmp/gi-chromatin-demo
python skills/gi-chromatin/gi_chromatin.py --input my_region.fa --output report_dir
python clawbio.py run gi-chromatin --demoThe skill requires a Genomic Intelligence partner key in GI_API_KEY. Resolution order:
--api-key <value> CLI flag (explicit override).GI_API_KEY environment variable.RuntimeError pointing here.A shared hackathon-tier key ships in .env.example at the repo root (opt-in only). Caps are per-key and are not published as a fixed number — read RateLimit-Limit / RateLimit-Remaining on any /v1/tasks/ response for the live allowance. The runner keeps them for you: they are in result.json under rate_limit, and a 429 names them on the error line. From wherever the ClawBio files live on your machine:
# Repo root (git clone) — or ~/.claude/plugins/cache/clawbio/clawbio/<version>/ for plugin installs
cp .env.example .env
set -a && source .env && set +aRequest an individual key at contact@genomicintelligence.ai, then:
export GI_API_KEY=gi_yourkeyherepython clawbio.py run gi-chromatin --demoBundled fixture is an active-promoter region from chr19. Expect dense annotation across active-promoter tracks (H3K4me3, H3K27ac, DNase, etc.) and many called windows.
result.json. The report.md summarizes; mine result.json programmatically for specific tracks.data.tracks.minLength / maxLength on ChromatinPredictRequest and counted after whitespace is stripped. Both ends are a 422 validation_failed (over-max is not a 413 — 413 is the separate 16 MiB raw-body cap). The skill rejects either locally before spending a request.bio_spec.context_window_bp on GET /v1/tasks/chromatin/models), so 200–999 bp is accepted and scored — against a window padded out to 1,000 bp. The skill warns when you are under it.GI_API_KEY for heavier use.output_dir/
├── report.md
├── result.json
└── reproducibility/
├── command.sh
└── environment.jsonRoutes here on: "chromatin", "histone marks", "DNase", "ATAC", "TF binding", "DeepSEA".
Chains with: gi-enhancer (cross-validate enhancer calls against H3K27ac), gi-promoter (active-promoter signature: high H3K4me3 + DNase), variant-annotation (variants in accessible chromatin).
Research and development use. Not for clinical or diagnostic decisions.
ClawBio/ClawBio
c7cf52b
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.