gi-chromatin

🧶 gi-chromatin

You 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. Prefer a browser? The same models run interactively at https://genomicintelligence.ai. Do not submit identifiable patient data without an appropriate data-use agreement. Key setup: see Authentication below.

Trigger

Fire this skill when the user says any of:

• "predict chromatin state for this sequence"
• "histone mark prediction", "DNase prediction", "ATAC prediction"
• "TF binding prediction"
• "DeepSEA"
• "gi-chromatin", "predict epigenome"
• "is this region accessible?"

Do NOT fire when:

• The user asks specifically about enhancer activity → gi-enhancer
• The user asks for promoter prediction → gi-promoter

Why This Exists

• Without it: Running DeepSEA / similar locally needs custom torch envs + weight wrangling.
• With it: One CLI call → 919 track predictions per window, in seconds.
• Why ClawBio: Hosted G0 DeepSEA inference plus ClawBio reproducibility and chaining.

API Backed

POST https://api.genomicintelligence.ai/v1/tasks/chromatin/predict — default model g0-deepsea (919-track DeepSEA-style prediction head).

Workflow

1. Parse: single-record FASTA.
2. POST to /v1/tasks/chromatin/predict.
3. Render: report.md (window + total-annotation counts; per-track detail in result.json).

CLI Reference

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 --demo

Authentication

The skill requires a Genomic Intelligence partner key in GI_API_KEY. Resolution order:

1. --api-key <value> CLI flag (explicit override).
2. GI_API_KEY environment variable.
3. Otherwise: the skill raises a RuntimeError pointing here.

Quick start — ClawBio hackathon key

A shared hackathon-tier key ships in .env.example at the repo root (50 concurrent / 120 rpm, opt-in only). 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 +a

Production / heavier use

Request an individual key at [email protected], then:

export GI_API_KEY=gi_yourkeyhere

Demo

python clawbio.py run gi-chromatin --demo

Bundled fixture is an active-promoter region from chr19. Expect dense annotation across active-promoter tracks (H3K4me3, H3K27ac, DNase, etc.) and many called windows.

Gotchas

• Big response. 919 tracks × N windows → multi-MB result.json. The report.md summarizes; mine result.json programmatically for specific tracks.
• Track labels are in the response. Don't hardcode track indices — read the names from data.tracks.
• Pre-windowing is unnecessary — API strides internally.
• Hackathon key is shared — GI_API_KEY for heavier use.

Output Structure

output_dir/
├── report.md
├── result.json
└── reproducibility/
    ├── command.sh
    └── environment.json

Integration with Bio Orchestrator

Routes 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).

Safety

Research tool. Not a clinical assay.