[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MA5AFQTCHTJ227HAJ8MBWY":3,"skill-same:01M6MA5AFQTCHTJ227HAJ8MBWY":122},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":62,"linkOnly":63,"markdownContent":64,"markdownBody":65,"frontMatter":66,"refName":80,"commitSha":81,"skillDirectory":82,"forksCount":83,"repositoryHtmlUrl":84,"repositoryHomepageUrl":85,"ownerHtmlUrl":86,"ownerBlogUrl":87,"ownerDescription":88,"updatedAt":89,"install":90,"resources":103},"01M6MA5AFQTCHTJ227HAJ8MBWY","genomic-intelligence",null,"Predict regulatory features, gene structure, and expression directly from DNA sequence using Genomic Intelligence's hosted transformer DNA language models — no local GPU or model weights. Six tasks over a REST API and a hosted MCP server (keyless public demo): promoter regions, splice donor\u002Facceptor sites, enhancer activity, chromatin state, sequence-to-expression (log TPM), and de-novo gene annotation, plus a composite find-genes-then-predict-expression workflow. Use when the user has a gene symbol, a genomic region, or a DNA\u002FFASTA sequence and wants any of these predictions, mentions Genomic Intelligence, genomicintelligence.ai, api.genomicintelligence.ai, or mcp.genomicintelligence.ai.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fgenomic-intelligence\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61],"genomic intelligence","intelligence","DNA","FASTA","prediction","limits","rate","window","gene","for","at","predictions","de","expression","false","gene expression","MCP","local","structure","log","model","access","api","analysis","server","library","transcript","tasks","workflow","mcp server","2026-11-10 10:12:30",false,"---\nname: genomic-intelligence\ndescription: 'Predict regulatory features, gene structure, and expression directly from DNA sequence using Genomic Intelligence''s hosted transformer DNA language models — no local GPU or model weights. Six tasks over a REST API and a hosted MCP server (keyless public demo): promoter regions, splice donor\u002Facceptor sites, enhancer activity, chromatin state, sequence-to-expression (log TPM), and de-novo gene annotation, plus a composite find-genes-then-predict-expression workflow. Use when the user has a gene symbol, a genomic region, or a DNA\u002FFASTA sequence and wants any of these predictions, mentions Genomic Intelligence, genomicintelligence.ai, api.genomicintelligence.ai, or mcp.genomicintelligence.ai.'\nlicense: MIT\ncompatibility: Python 3.10+ with the `requests` library for the REST path (no dedicated SDK). Network access required. The REST `\u002Fv1` API needs a `GI_API_KEY` (a `gi_` bearer); the hosted MCP server at mcp.genomicintelligence.ai\u002Fmcp works keyless against a rate- and concurrency-limited public demo tier, key optional.\nmetadata:\n  version: '1.2'\n  category: life-sciences\n  maintainer: Kalaris Labs\n  trigger-keywords: DNA sequence prediction, regulatory genomics, promoter prediction, splice site prediction, enhancer activity, chromatin state, gene expression prediction, sequence to expression, log TPM, gene annotation, transcript prediction, DNA language model, genomic intelligence, hosted inference, Ensembl sequence, FASTA prediction, cis-regulatory, TSS window, DeepSEA, DeepSTARR, BigBird splice, MCP genomics\n  openclaw:\n    primaryEnv: GI_API_KEY\n    envVars:\n    - name: GI_API_KEY\n      required: false\n      description: Optional gi_ bearer key for the REST \u002Fv1 API and higher MCP rate and concurrency limits. The hosted MCP demo runs keyless; request a key at contact@genomicintelligence.ai.\n  contributor: Genomic Intelligence\n  tags: DNA language models, regulatory genomics, gene structure, sequence analysis\n---\n\n# Genomic Intelligence — DNA Sequence Models\n\nGenomic Intelligence (GI) serves transformer DNA language models over six\nsequence-analysis tasks on managed GPUs. Give it a **gene symbol**, a **genomic\nregion**, or a **DNA\u002FFASTA sequence**; it returns structured predictions —\npromoter regions, splice sites, enhancer activity, chromatin state, expression\n(log TPM), and de-novo gene annotation. Nothing runs locally: no model weights,\nno GPU, no heavy Python stack. It is a thin client over a hosted, versioned\ninference API.\n\n**Official docs:** [docs.genomicintelligence.ai](https:\u002F\u002Fdocs.genomicintelligence.ai) ·\nREST contract at [api.genomicintelligence.ai\u002Fv1\u002Fopenapi.json](https:\u002F\u002Fapi.genomicintelligence.ai\u002Fv1\u002Fopenapi.json) ·\nhosted MCP server at `https:\u002F\u002Fmcp.genomicintelligence.ai\u002Fmcp`\n\n## When to use this skill\n\nUse GI when the user has DNA and wants a model prediction:\n\n- **Find promoters** in a genomic region (`promoter`)\n- **Predict splice** donor\u002Facceptor sites (`splice`)\n- **Score enhancer activity** — developmental & housekeeping (`enhancer`)\n- **Annotate chromatin state** across hundreds of tracks (`chromatin`)\n- **Predict expression** as log(TPM+1) from a sequence + cell-type context (`expression`)\n- **Annotate genes\u002Ftranscripts** de novo, no reference needed (`annotation`)\n- **Find the genes in a region and predict each one's expression** (composite)\n\nNot for local alignment, variant calling, or file I\u002FO — use a local tool\n(BioPython, bcftools) for those. GI is for **model inference from sequence**.\n\n> Research and development use. Not for clinical or diagnostic decisions.\n\n## Two ways to call GI\n\n### Hosted MCP server (keyless; preferred on MCP hosts)\n\nGI hosts an MCP server at `https:\u002F\u002Fmcp.genomicintelligence.ai\u002Fmcp` (Streamable\nHTTP). When your agent host supports MCP, prefer it: it works **keyless** against\na rate- and concurrency-limited public demo tier, and an optional `gi_` bearer\nkey raises those limits. It exposes acquisition tools that return a **sequence handle**\n(`sequence_ref`) and `predict_*` tools that take that handle, so large sequences\nstay out of the context. See [MCP workflow](#mcp-workflow-handle-based) below and\n`references\u002Fmcp.md`.\n\n### REST API (universal)\n\nPlain HTTP with `requests` against `https:\u002F\u002Fapi.genomicintelligence.ai\u002Fv1`. The\nREST path **requires** a `GI_API_KEY` (a `gi_` bearer). Use it on any host, in\nscripts, or when you need the raw envelope. See [Core REST workflow](#core-rest-workflow).\n\n## Access and authentication\n\n1. The **hosted MCP demo is keyless** — try it with nothing set.\n2. The **REST `\u002Fv1` API needs a key**, sent as `Authorization: Bearer \u003Ckey>`.\n   Request one at [contact@genomicintelligence.ai](mailto:contact@genomicintelligence.ai).\n3. **Never hardcode the key.** Read it from the `GI_API_KEY` environment variable\n   (or a `.env` via `python-dotenv`). Never commit keys.\n\n```bash\nexport GI_API_KEY=\"gi_yourkeyhere\"     # optional for MCP; required for REST\nexport GI_BASE_URL=\"https:\u002F\u002Fapi.genomicintelligence.ai\"   # override for staging\n```\n\nKeys are scoped to a partner tier with concurrency and per-minute caps. A `429`\nmeans you hit a cap — back off and retry, or ask GI to raise your tier.\n\n## The six tasks\n\nEach task is **its own published operation** with its own request schema, its own\nminimum length, and its own closed `options` object — `POST\n\u002Fv1\u002Ftasks\u002Fpromoter\u002Fpredict`, `\u002Fv1\u002Ftasks\u002Fsplice\u002Fpredict`,\n`\u002Fv1\u002Ftasks\u002Fenhancer\u002Fpredict`, `\u002Fv1\u002Ftasks\u002Fchromatin\u002Fpredict`,\n`\u002Fv1\u002Ftasks\u002Fannotation\u002Fpredict`, `\u002Fv1\u002Ftasks\u002Fexpression\u002Fpredict`. Each path is a\nliteral string, so nothing needs to be constructed, and there is no shared\n`PredictRequest` schema. Body is `{sequence, sequence_name?, model?,\noptions?}`, returning a `{data, meta}` envelope. What differs per task:\n\n| Task | Recommended mode | Accepted length | `context_window_bp` | Notes |\n|---|---|---|---|---|\n| `promoter` | sync | 300–500,000 bp | 2,000 bp | sliding-window promoter regions |\n| `splice` | sync | 100–500,000 bp | 15,000 bp | donor\u002Facceptor sites (long-context BigBird); strand-specific — feed transcript orientation |\n| `enhancer` | sync | 50–500,000 bp | 249 bp | dev + housekeeping scores (DeepSTARR, *Drosophila*) |\n| `chromatin` | sync | 200–500,000 bp | 1,000 bp | hundreds of tracks (DeepSEA) |\n| `expression` | sync | **9,198–500,000 bp** | n\u002Fa (`trained_window_bp` 9,198) | log(TPM+1); needs `tss_index` unless exactly 9,198 bp, plus a cell-type `description` |\n| `annotation` | async | 1,000–500,000 bp | n\u002Fa | de-novo transcripts; submit + poll; sync above 200,000 bp is `413 sync_too_large` |\n\n`Recommended mode` is guidance, not a constraint — every task accepts both. Omit `Prefer` for a synchronous `200`; send `Prefer: respond-async` for a `202` plus `GET \u002Fv1\u002Ftasks\u002Fjobs\u002F{job_id}`. The one enforced limit is per operation: where `\u002Fv1\u002Fopenapi.json` publishes `x-sync-limit-bp` on a `POST`, a synchronous request above that length is `413 sync_too_large` — 200,000 bp on `annotation` and 50,000 bp on the composite workflow as of `info.version` 2026.09.10.1. Read the field rather than memorising the numbers; the other predict tasks carry no limit today.\n\n**The minimum is admission control, not regime.** A request above the floor but\nshorter than the selected model's `bio_spec.context_window_bp` is *accepted and\nscored* — against a window padded out to the context window. Enhancer is the\nsharp case: the floor is 50 bp but the context window is 249 bp, so 50–248 bp is\nscored mostly on padding. Compare your length against\n`context_window_bp` from `GET \u002Fv1\u002Ftasks\u002F{task}\u002Fmodels` to know whether the model\nsaw real sequence. Longer-than-context input is fine — the scanner steps a\nprediction window at a time and pads only the final partial window.\n\nUnder the floor and over the 500,000 bp cap are **both `422 validation_failed`**\nat `loc [\"body\",\"sequence\"]`; over-length is *not* a `413`. All lengths are\nmeasured after whitespace is stripped, so a line-wrapped FASTA body can be pasted\nverbatim (a `>` header line still fails the alphabet check).\n\n`options` is typed and **closed** (`additionalProperties: false`) per task — an\nunknown key is a hard `422 validation_failed` with `type: \"extra_forbidden\"`,\nnever ignored:\n\n| Task | `options` keys |\n|---|---|\n| promoter | `threshold` (0–1, default 0.5) |\n| splice | `threshold` (0–1, default 0.5), `site_types` (subset of `[\"donor\",\"acceptor\"]`, default both) |\n| enhancer | *(none)* |\n| chromatin | `threshold` (0–1, default 0.5) |\n| annotation | `batch_size` (1–128, default 8), `shift_coordinates`, `reverse_complement` (default true) |\n| expression | `description` — **required**, and the only key |\n\n`Prefer: respond-async` is a declared header on **all six** predict operations\nand on the composite, not just `annotation` — see [Async](#async-any-task-recommended-for-annotation).\n\n**Omit `model` and the API uses the task's default** — that is the recommended\ncall. Default model IDs are intentionally **not** documented here: defaults\nchange and retired IDs fail hard, so never hardcode one. To pin a model, or to\npick a non-human one (Drosophila, yeast, and Arabidopsis models exist for several\ntasks), discover IDs at call time with `GET \u002Fv1\u002Ftasks\u002F{task}\u002Fmodels` (REST) or\n`list_models` (MCP) — and **never invent one**. Full per-task output shapes are\nin `references\u002Ftasks.md`.\n\n`expression` is the strictest of the six: alone among them its schema requires\n`options` as well as `sequence`. Three hard rules it enforces — every violation\nis a `422`, nothing is padded or clamped, and there is no opt-out flag, header,\nor query parameter:\n\n- **It always scores exactly one 9,198 bp TSS-centred window** —\n  `sequence[tss_index-4599 : tss_index+4599]`. The endpoint itself accepts\n  **9,198–500,000 bp**; anything below 9,198 bp is rejected outright.\n- **`tss_index` is required unless the sequence is exactly 9,198 bp.** It is the\n  0-based TSS offset into the **whitespace-stripped** sequence, bounded by\n  `4599 ≤ tss_index ≤ len(sequence) − 4599`. At exactly 9,198 bp it defaults to\n  4,599, the only legal value there. So you may submit a whole locus (up to\n  500 kb) and let the server cut the window — but the server does **not**\n  discover the TSS for you (that is the composite workflow's job), and does\n  **not** reverse-complement: submit gene-sense sequence.\n- **`options.description`** — a cell-type \u002F assay string (e.g. `\"K562 cells\"`) —\n  is required, and is the **only** key `expression` accepts inside `options`.\n  Unknown top-level body fields are rejected too.\n\n> Note: the legal `tss_index` range is wide, so an offset that is merely\n> *wrong* (counted over raw FASTA characters including newlines, or relative to\n> a locus start rather than the submitted slice) does not error — it returns a\n> confident `200` for the wrong window. Assert on\n> `meta.task_specific_counts.scored_window` \u002F `.tss_index` in the response.\n> The length you submitted is `meta.sequence_length` (also echoed as\n> `data.input.submitted_sequence_length`); the scored width is always 9,198,\n> i.e. `scored_window[1] - scored_window[0]`. (`data.input.sequence_length`\n> was removed at contract revision 13.)\n>\n> Both `tss_index` violations — \"required unless exactly 9,198 bp\" and the range\n> check — come from a whole-model validator, so they surface at the body level\n> rather than under `tss_index`. Match on `error.code == \"validation_failed\"`\n> and use the message for display only. Any `loc` tuple quoted in this skill is\n> illustrative of that shape, not part of the contract: it is not published in\n> the schema and must not be branched on.\n\n## Sequence acquisition\n\nYou rarely start from a raw 9,198 bp string. Acquire sequence first:\n\n- **From a gene symbol** → MCP `fetch_ensembl_sequence(gene=...)`; **from\n  coordinates** → `fetch_region(region=...)`. Both fetch public Ensembl reference\n  sequence (no key). REST users can query Ensembl REST directly. (`find_genes` is\n  the annotation task, not an acquisition tool.)\n- **For `expression`** → use the TSS-centred fetch so the window is exactly\n  9,198 bp. MCP: `fetch_gene_for_expression` (handles the centring). Otherwise\n  fetch a wider locus and pass the TSS as `tss_index` so the server cuts the\n  window — but compute that offset on the stripped nucleotide string, not on\n  file characters.\n- **From a local FASTA** → MCP `store_inline_sequence`, or read the file yourself\n  for REST. (`load_local_fasta` exists only in local deployments, not on the\n  hosted server.)\n- **A demo sequence** → MCP `load_demo_sequence(name=...)` returns a ready handle\n  for a keyless smoke test; `name` is required.\n\nSee `references\u002Fsequence-acquisition.md` for the exact Ensembl calls and the\nexpression-window math.\n\n## Core REST workflow\n\nCalled synchronously — the default for every task — a prediction is one call:\n\n```python\nimport os, requests\n\nBASE = os.environ.get(\"GI_BASE_URL\", \"https:\u002F\u002Fapi.genomicintelligence.ai\")\nHEADERS = {\"Authorization\": f\"Bearer {os.environ['GI_API_KEY']}\"}\n\ndef predict(task, sequence, sequence_name, model=None, options=None, tss_index=None):\n    body = {\"sequence\": sequence, \"sequence_name\": sequence_name}\n    if model:   body[\"model\"] = model\n    if options: body[\"options\"] = options\n    if tss_index is not None: body[\"tss_index\"] = tss_index   # expression only\n    # Each task is its own published operation, but the URL string is unchanged.\n    r = requests.post(f\"{BASE}\u002Fv1\u002Ftasks\u002F{task}\u002Fpredict\", headers=HEADERS, json=body)\n    # 422 validation_failed  — sequence under the task floor OR over 500,000 bp,\n    #                          bad tss_index, missing options.description,\n    #                          or ANY unknown body\u002Foptions key (options is closed)\n    # 401 no\u002Fbad key · 404 unknown task · 413 body over 16 MiB · 429 rate limit\n    r.raise_for_status()\n    return r.json()               # {\"data\": {...}, \"meta\": {...}}\n\n# Promoter:\nout = predict(\"promoter\", seq, \"TP53_region\")\nprint(out[\"data\"][\"summary\"])\n\n# Expression — a pre-cut 9,198 bp TSS-centred window (tss_index defaults to 4,599):\nout = predict(\"expression\", tss_window_9198bp, \"HBB\",\n              options={\"description\": \"K562 cells\"})\nprint(out[\"data\"][\"prediction\"][\"expression_log_tpm\"])\n\n# Expression — a whole locus; the server slices ±4,599 bp around the TSS you name.\n# tss_index is 0-based into the whitespace-stripped sequence.\nout = predict(\"expression\", locus_seq, \"HBB\",\n              options={\"description\": \"K562 cells\"}, tss_index=tss_offset_in_locus)\nprint(out[\"meta\"][\"task_specific_counts\"][\"scored_window\"])   # confirm the window scored\n```\n\n### Async (any task; recommended for annotation)\n\n`Prefer: respond-async` is a declared header parameter on all six predict\noperations and on the composite. A `202` carries the same `{data, meta}` envelope\nas a sync `200`, with `data = {job_id, status: \"accepted\", links}`; the job id is\nalso in the `Content-Location` and `X-Job-Id` response headers. Async is\nJSON-only — combining it with a text `format` is rejected. `annotation` is the\ntask that needs it:\n\n```python\nimport time\n\nr = requests.post(f\"{BASE}\u002Fv1\u002Ftasks\u002Fannotation\u002Fpredict\",\n                  headers={**HEADERS, \"Prefer\": \"respond-async\"},\n                  json={\"sequence\": seq, \"sequence_name\": \"TP53\"})\nr.raise_for_status()              # 202 Accepted\njob_id = r.json()[\"data\"][\"job_id\"]\n\nwhile True:\n    j = requests.get(f\"{BASE}\u002Fv1\u002Ftasks\u002Fjobs\u002F{job_id}\", headers=HEADERS)\n    if j.status_code == 200:      # terminal: body is the final {data, meta}\n        break\n    j.raise_for_status()          # 202 = still running (2xx, won't raise)\n    time.sleep(5)                 # ~20 s typical for ~20 kb\ntranscripts = j.json()[\"data\"][\"transcripts\"]\n```\n\n## MCP workflow (handle-based)\n\nOn an MCP host, acquire a handle, then predict against it — sequences stay out of\nthe context:\n\n```\n# 1. Acquire a sequence handle (each returns a sequence_ref):\nload_demo_sequence(name=\"promoter_tp53\")  # keyless smoke test; name is required\nfetch_ensembl_sequence(gene=\"TP53\")       # gene symbol or Ensembl ID -> handle\nfetch_region(region=\"chr11:5,225,000-5,235,000\")   # coordinates -> handle\nfetch_gene_for_expression(gene=\"HBB\")     # TSS-centred 9,198 bp handle for expression\n\n# 2. Predict against the handle:\npredict_promoter(sequence_ref=\u003Cref>)\npredict_expression(sequence_ref=\u003Cref>, description=\"K562 cells\")\npredict_splice(sequence_ref=\u003Cref>)        # + predict_enhancer \u002F predict_chromatin\n\n# 3. Annotation on MCP is `find_genes` (there is no predict_annotation).\n#    It takes a handle, not a region, and runs async internally:\nfind_genes(sequence_ref=\u003Cref>)            # wait=True (default) returns the result\nfind_genes(sequence_ref=\u003Cref>, wait=False)  # -> job_id; poll get_job(job_id)\n\n# Discover models with list_models(task); reference context lives in the\n# gi:\u002F\u002Fmodels, gi:\u002F\u002Fdocs\u002Ftasks, and gi:\u002F\u002Faccount MCP resources.\n```\n\n## Composite: find genes, then predict expression\n\nTo answer \"what genes are in this region and how are they expressed?\", use the\ncomposite:\n\n- **MCP:** `find_genes_and_predict_expression(sequence_ref=..., description=...)`\n  — takes a **handle, not a region** (acquire one with `fetch_region` first);\n  `description` is required. Finds genes in the sequence and returns an\n  expression prediction for each.\n- **REST:** one call — `POST \u002Fv1\u002Fworkflows\u002Ffind-genes-and-predict-expression`,\n  body `{sequence, options}` with `sequence` 1,000–500,000 bp and\n  `options.description` (cell type \u002F assay) required; a missing or empty\n  description is a `422 validation_failed`. It annotates, centres a 9,198 bp\n  window on each discovered gene's TSS (padding with `N` up to half the window\n  rather than dropping an edge gene), and returns a prediction per gene.\n  `meta.task_specific_counts` = `{genes_found, genes_predicted, genes_skipped}`\n  with `genes_predicted + genes_skipped == genes_found`; per-gene causes in\n  `data.expression_predictions[].skip_reason`. Above **50,000 bp** (its `x-sync-limit-bp`) it forces\n  async: a synchronous request over that size is `413 sync_too_large` with\n  `error.details = {sequence_length, threshold}` — retry the same body with\n  `Prefer: respond-async`.\n\n## Errors\n\n| Code | `error.code` | Meaning | Action |\n|---|---|---|---|\n| 400 | `bad_request` | Malformed request | Check the body shape |\n| 401 \u002F 403 | `unauthorized` \u002F `forbidden` | Missing\u002Finvalid key (REST) | Set `GI_API_KEY`; or use the keyless MCP demo |\n| 404 | `not_found` | **Unknown task** (`\u002Fv1\u002Ftasks\u002Fbogus\u002Fpredict`) or unknown job | Check the task name — an unrecognised task is a 404, not a 422 |\n| 413 | `payload_too_large` | Raw request body over **16 MiB** | Split the input — this is the body cap, not the sequence cap |\n| 413 | `sync_too_large` | Synchronous request above the operation's `x-sync-limit-bp` (200,000 bp on `annotation`, 50,000 bp on the composite) | Retry with `Prefer: respond-async` |\n| 415 | `unsupported_format` | Unsupported `format` query value | Use a format the task supports; there is no silent fallback to JSON |\n| 422 | `validation_failed` | The most common failure: sequence **under the task floor or over 500,000 bp**, expression below 9,198 bp, a missing\u002Fout-of-range `tss_index`, a missing `options.description`, or **any unknown body or `options` key** | Read the message; fix the body |\n| 429 | `rate_limited` \u002F `too_many_requests` | Rate \u002F concurrency cap | Back off (honour `Retry-After`); ask GI to raise your tier |\n| 5xx | `internal_error` \u002F `service_unavailable` \u002F `model_loading` \u002F `timeout` | Server error | Retry; if persistent, contact support |\n\n`error.code` is a closed 21-value enum (`bad_request`, `unauthorized`,\n`forbidden`, `not_found`, `conflict`, `job_expired`, `payload_too_large`,\n`sync_too_large`, `unsupported_format`, `validation_failed`,\n`too_many_requests`, `rate_limited`, `internal_error`, `timeout`,\n`insufficient_memory`, `model_not_found`, `task_not_supported_by_model`,\n`model_loading`, `service_unavailable`, `http_error`, `unknown`); treat an\nunlisted value as a generic failure, not a parse error.\n\n**Branch on `code`, never on `details` or `loc`.** `details` is keyed on the\nsibling `code`; for `validation_failed` it is the `{errors: [{loc, msg, type}, …]}`\nobject the schema declares. Treat it as display-only — `code` is the stable\ndiscriminator.\n\nFor correlation, `error.request_id` and the `X-Request-Id` **header** are both\nset on every response, and success envelopes carry `meta.request_id`. Reading\nthe header first remains a safe default.\nEvery response carries `RateLimit-Limit`, `RateLimit-Remaining`,\n`RateLimit-Reset`, `RateLimit-Policy`; a `429` adds `Retry-After`.\n\n> Verified against OpenAPI `info.version` **2026.08.20.7**. The contract moves,\n> and `info.version` in `\u002Fv1\u002Fopenapi.json` reports what a given deployment\n> serves: if it is ahead of the version above, re-check the numbers in this file\n> against that document, which is the arbiter if the two disagree.\n\n## Reference files\n\n- `references\u002Ftasks.md` — per-task output shapes, model registries, the async\n  annotation contract.\n- `references\u002Fapi-and-auth.md` — REST endpoints, the `{data, meta}` envelope,\n  auth, base-URL override, tiers.\n- `references\u002Fmcp.md` — the hosted MCP tool list, the handle-based flow, and the\n  `gi:\u002F\u002F` resources.\n- `references\u002Fsequence-acquisition.md` — Ensembl fetch calls and the\n  expression-window (9,198 bp, TSS-centred) math, including `tss_index`.\n\n## Related skills\n\n- `arboreto`: Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3).\n- `tamarind`: Access a collection of open-source molecular design and structural biology tools on the Tamarind Bio platform, via its REST API or MCP serv…\n","# Genomic Intelligence — DNA Sequence Models\n\nGenomic Intelligence (GI) serves transformer DNA language models over six\nsequence-analysis tasks on managed GPUs. Give it a **gene symbol**, a **genomic\nregion**, or a **DNA\u002FFASTA sequence**; it returns structured predictions —\npromoter regions, splice sites, enhancer activity, chromatin state, expression\n(log TPM), and de-novo gene annotation. Nothing runs locally: no model weights,\nno GPU, no heavy Python stack. It is a thin client over a hosted, versioned\ninference API.\n\n**Official docs:** [docs.genomicintelligence.ai](https:\u002F\u002Fdocs.genomicintelligence.ai) ·\nREST contract at [api.genomicintelligence.ai\u002Fv1\u002Fopenapi.json](https:\u002F\u002Fapi.genomicintelligence.ai\u002Fv1\u002Fopenapi.json) ·\nhosted MCP server at `https:\u002F\u002Fmcp.genomicintelligence.ai\u002Fmcp`\n\n## When to use this skill\n\nUse GI when the user has DNA and wants a model prediction:\n\n- **Find promoters** in a genomic region (`promoter`)\n- **Predict splice** donor\u002Facceptor sites (`splice`)\n- **Score enhancer activity** — developmental & housekeeping (`enhancer`)\n- **Annotate chromatin state** across hundreds of tracks (`chromatin`)\n- **Predict expression** as log(TPM+1) from a sequence + cell-type context (`expression`)\n- **Annotate genes\u002Ftranscripts** de novo, no reference needed (`annotation`)\n- **Find the genes in a region and predict each one's expression** (composite)\n\nNot for local alignment, variant calling, or file I\u002FO — use a local tool\n(BioPython, bcftools) for those. GI is for **model inference from sequence**.\n\n> Research and development use. Not for clinical or diagnostic decisions.\n\n## Two ways to call GI\n\n### Hosted MCP server (keyless; preferred on MCP hosts)\n\nGI hosts an MCP server at `https:\u002F\u002Fmcp.genomicintelligence.ai\u002Fmcp` (Streamable\nHTTP). When your agent host supports MCP, prefer it: it works **keyless** against\na rate- and concurrency-limited public demo tier, and an optional `gi_` bearer\nkey raises those limits. It exposes acquisition tools that return a **sequence handle**\n(`sequence_ref`) and `predict_*` tools that take that handle, so large sequences\nstay out of the context. See [MCP workflow](#mcp-workflow-handle-based) below and\n`references\u002Fmcp.md`.\n\n### REST API (universal)\n\nPlain HTTP with `requests` against `https:\u002F\u002Fapi.genomicintelligence.ai\u002Fv1`. The\nREST path **requires** a `GI_API_KEY` (a `gi_` bearer). Use it on any host, in\nscripts, or when you need the raw envelope. See [Core REST workflow](#core-rest-workflow).\n\n## Access and authentication\n\n1. The **hosted MCP demo is keyless** — try it with nothing set.\n2. The **REST `\u002Fv1` API needs a key**, sent as `Authorization: Bearer \u003Ckey>`.\n   Request one at [contact@genomicintelligence.ai](mailto:contact@genomicintelligence.ai).\n3. **Never hardcode the key.** Read it from the `GI_API_KEY` environment variable\n   (or a `.env` via `python-dotenv`). Never commit keys.\n\n```bash\nexport GI_API_KEY=\"gi_yourkeyhere\"     # optional for MCP; required for REST\nexport GI_BASE_URL=\"https:\u002F\u002Fapi.genomicintelligence.ai\"   # override for staging\n```\n\nKeys are scoped to a partner tier with concurrency and per-minute caps. A `429`\nmeans you hit a cap — back off and retry, or ask GI to raise your tier.\n\n## The six tasks\n\nEach task is **its own published operation** with its own request schema, its own\nminimum length, and its own closed `options` object — `POST\n\u002Fv1\u002Ftasks\u002Fpromoter\u002Fpredict`, `\u002Fv1\u002Ftasks\u002Fsplice\u002Fpredict`,\n`\u002Fv1\u002Ftasks\u002Fenhancer\u002Fpredict`, `\u002Fv1\u002Ftasks\u002Fchromatin\u002Fpredict`,\n`\u002Fv1\u002Ftasks\u002Fannotation\u002Fpredict`, `\u002Fv1\u002Ftasks\u002Fexpression\u002Fpredict`. Each path is a\nliteral string, so nothing needs to be constructed, and there is no shared\n`PredictRequest` schema. Body is `{sequence, sequence_name?, model?,\noptions?}`, returning a `{data, meta}` envelope. What differs per task:\n\n| Task | Recommended mode | Accepted length | `context_window_bp` | Notes |\n|---|---|---|---|---|\n| `promoter` | sync | 300–500,000 bp | 2,000 bp | sliding-window promoter regions |\n| `splice` | sync | 100–500,000 bp | 15,000 bp | donor\u002Facceptor sites (long-context BigBird); strand-specific — feed transcript orientation |\n| `enhancer` | sync | 50–500,000 bp | 249 bp | dev + housekeeping scores (DeepSTARR, *Drosophila*) |\n| `chromatin` | sync | 200–500,000 bp | 1,000 bp | hundreds of tracks (DeepSEA) |\n| `expression` | sync | **9,198–500,000 bp** | n\u002Fa (`trained_window_bp` 9,198) | log(TPM+1); needs `tss_index` unless exactly 9,198 bp, plus a cell-type `description` |\n| `annotation` | async | 1,000–500,000 bp | n\u002Fa | de-novo transcripts; submit + poll; sync above 200,000 bp is `413 sync_too_large` |\n\n`Recommended mode` is guidance, not a constraint — every task accepts both. Omit `Prefer` for a synchronous `200`; send `Prefer: respond-async` for a `202` plus `GET \u002Fv1\u002Ftasks\u002Fjobs\u002F{job_id}`. The one enforced limit is per operation: where `\u002Fv1\u002Fopenapi.json` publishes `x-sync-limit-bp` on a `POST`, a synchronous request above that length is `413 sync_too_large` — 200,000 bp on `annotation` and 50,000 bp on the composite workflow as of `info.version` 2026.09.10.1. Read the field rather than memorising the numbers; the other predict tasks carry no limit today.\n\n**The minimum is admission control, not regime.** A request above the floor but\nshorter than the selected model's `bio_spec.context_window_bp` is *accepted and\nscored* — against a window padded out to the context window. Enhancer is the\nsharp case: the floor is 50 bp but the context window is 249 bp, so 50–248 bp is\nscored mostly on padding. Compare your length against\n`context_window_bp` from `GET \u002Fv1\u002Ftasks\u002F{task}\u002Fmodels` to know whether the model\nsaw real sequence. Longer-than-context input is fine — the scanner steps a\nprediction window at a time and pads only the final partial window.\n\nUnder the floor and over the 500,000 bp cap are **both `422 validation_failed`**\nat `loc [\"body\",\"sequence\"]`; over-length is *not* a `413`. All lengths are\nmeasured after whitespace is stripped, so a line-wrapped FASTA body can be pasted\nverbatim (a `>` header line still fails the alphabet check).\n\n`options` is typed and **closed** (`additionalProperties: false`) per task — an\nunknown key is a hard `422 validation_failed` with `type: \"extra_forbidden\"`,\nnever ignored:\n\n| Task | `options` keys |\n|---|---|\n| promoter | `threshold` (0–1, default 0.5) |\n| splice | `threshold` (0–1, default 0.5), `site_types` (subset of `[\"donor\",\"acceptor\"]`, default both) |\n| enhancer | *(none)* |\n| chromatin | `threshold` (0–1, default 0.5) |\n| annotation | `batch_size` (1–128, default 8), `shift_coordinates`, `reverse_complement` (default true) |\n| expression | `description` — **required**, and the only key |\n\n`Prefer: respond-async` is a declared header on **all six** predict operations\nand on the composite, not just `annotation` — see [Async](#async-any-task-recommended-for-annotation).\n\n**Omit `model` and the API uses the task's default** — that is the recommended\ncall. Default model IDs are intentionally **not** documented here: defaults\nchange and retired IDs fail hard, so never hardcode one. To pin a model, or to\npick a non-human one (Drosophila, yeast, and Arabidopsis models exist for several\ntasks), discover IDs at call time with `GET \u002Fv1\u002Ftasks\u002F{task}\u002Fmodels` (REST) or\n`list_models` (MCP) — and **never invent one**. Full per-task output shapes are\nin `references\u002Ftasks.md`.\n\n`expression` is the strictest of the six: alone among them its schema requires\n`options` as well as `sequence`. Three hard rules it enforces — every violation\nis a `422`, nothing is padded or clamped, and there is no opt-out flag, header,\nor query parameter:\n\n- **It always scores exactly one 9,198 bp TSS-centred window** —\n  `sequence[tss_index-4599 : tss_index+4599]`. The endpoint itself accepts\n  **9,198–500,000 bp**; anything below 9,198 bp is rejected outright.\n- **`tss_index` is required unless the sequence is exactly 9,198 bp.** It is the\n  0-based TSS offset into the **whitespace-stripped** sequence, bounded by\n  `4599 ≤ tss_index ≤ len(sequence) − 4599`. At exactly 9,198 bp it defaults to\n  4,599, the only legal value there. So you may submit a whole locus (up to\n  500 kb) and let the server cut the window — but the server does **not**\n  discover the TSS for you (that is the composite workflow's job), and does\n  **not** reverse-complement: submit gene-sense sequence.\n- **`options.description`** — a cell-type \u002F assay string (e.g. `\"K562 cells\"`) —\n  is required, and is the **only** key `expression` accepts inside `options`.\n  Unknown top-level body fields are rejected too.\n\n> Note: the legal `tss_index` range is wide, so an offset that is merely\n> *wrong* (counted over raw FASTA characters including newlines, or relative to\n> a locus start rather than the submitted slice) does not error — it returns a\n> confident `200` for the wrong window. Assert on\n> `meta.task_specific_counts.scored_window` \u002F `.tss_index` in the response.\n> The length you submitted is `meta.sequence_length` (also echoed as\n> `data.input.submitted_sequence_length`); the scored width is always 9,198,\n> i.e. `scored_window[1] - scored_window[0]`. (`data.input.sequence_length`\n> was removed at contract revision 13.)\n>\n> Both `tss_index` violations — \"required unless exactly 9,198 bp\" and the range\n> check — come from a whole-model validator, so they surface at the body level\n> rather than under `tss_index`. Match on `error.code == \"validation_failed\"`\n> and use the message for display only. Any `loc` tuple quoted in this skill is\n> illustrative of that shape, not part of the contract: it is not published in\n> the schema and must not be branched on.\n\n## Sequence acquisition\n\nYou rarely start from a raw 9,198 bp string. Acquire sequence first:\n\n- **From a gene symbol** → MCP `fetch_ensembl_sequence(gene=...)`; **from\n  coordinates** → `fetch_region(region=...)`. Both fetch public Ensembl reference\n  sequence (no key). REST users can query Ensembl REST directly. (`find_genes` is\n  the annotation task, not an acquisition tool.)\n- **For `expression`** → use the TSS-centred fetch so the window is exactly\n  9,198 bp. MCP: `fetch_gene_for_expression` (handles the centring). Otherwise\n  fetch a wider locus and pass the TSS as `tss_index` so the server cuts the\n  window — but compute that offset on the stripped nucleotide string, not on\n  file characters.\n- **From a local FASTA** → MCP `store_inline_sequence`, or read the file yourself\n  for REST. (`load_local_fasta` exists only in local deployments, not on the\n  hosted server.)\n- **A demo sequence** → MCP `load_demo_sequence(name=...)` returns a ready handle\n  for a keyless smoke test; `name` is required.\n\nSee `references\u002Fsequence-acquisition.md` for the exact Ensembl calls and the\nexpression-window math.\n\n## Core REST workflow\n\nCalled synchronously — the default for every task — a prediction is one call:\n\n```python\nimport os, requests\n\nBASE = os.environ.get(\"GI_BASE_URL\", \"https:\u002F\u002Fapi.genomicintelligence.ai\")\nHEADERS = {\"Authorization\": f\"Bearer {os.environ['GI_API_KEY']}\"}\n\ndef predict(task, sequence, sequence_name, model=None, options=None, tss_index=None):\n    body = {\"sequence\": sequence, \"sequence_name\": sequence_name}\n    if model:   body[\"model\"] = model\n    if options: body[\"options\"] = options\n    if tss_index is not None: body[\"tss_index\"] = tss_index   # expression only\n    # Each task is its own published operation, but the URL string is unchanged.\n    r = requests.post(f\"{BASE}\u002Fv1\u002Ftasks\u002F{task}\u002Fpredict\", headers=HEADERS, json=body)\n    # 422 validation_failed  — sequence under the task floor OR over 500,000 bp,\n    #                          bad tss_index, missing options.description,\n    #                          or ANY unknown body\u002Foptions key (options is closed)\n    # 401 no\u002Fbad key · 404 unknown task · 413 body over 16 MiB · 429 rate limit\n    r.raise_for_status()\n    return r.json()               # {\"data\": {...}, \"meta\": {...}}\n\n# Promoter:\nout = predict(\"promoter\", seq, \"TP53_region\")\nprint(out[\"data\"][\"summary\"])\n\n# Expression — a pre-cut 9,198 bp TSS-centred window (tss_index defaults to 4,599):\nout = predict(\"expression\", tss_window_9198bp, \"HBB\",\n              options={\"description\": \"K562 cells\"})\nprint(out[\"data\"][\"prediction\"][\"expression_log_tpm\"])\n\n# Expression — a whole locus; the server slices ±4,599 bp around the TSS you name.\n# tss_index is 0-based into the whitespace-stripped sequence.\nout = predict(\"expression\", locus_seq, \"HBB\",\n              options={\"description\": \"K562 cells\"}, tss_index=tss_offset_in_locus)\nprint(out[\"meta\"][\"task_specific_counts\"][\"scored_window\"])   # confirm the window scored\n```\n\n### Async (any task; recommended for annotation)\n\n`Prefer: respond-async` is a declared header parameter on all six predict\noperations and on the composite. A `202` carries the same `{data, meta}` envelope\nas a sync `200`, with `data = {job_id, status: \"accepted\", links}`; the job id is\nalso in the `Content-Location` and `X-Job-Id` response headers. Async is\nJSON-only — combining it with a text `format` is rejected. `annotation` is the\ntask that needs it:\n\n```python\nimport time\n\nr = requests.post(f\"{BASE}\u002Fv1\u002Ftasks\u002Fannotation\u002Fpredict\",\n                  headers={**HEADERS, \"Prefer\": \"respond-async\"},\n                  json={\"sequence\": seq, \"sequence_name\": \"TP53\"})\nr.raise_for_status()              # 202 Accepted\njob_id = r.json()[\"data\"][\"job_id\"]\n\nwhile True:\n    j = requests.get(f\"{BASE}\u002Fv1\u002Ftasks\u002Fjobs\u002F{job_id}\", headers=HEADERS)\n    if j.status_code == 200:      # terminal: body is the final {data, meta}\n        break\n    j.raise_for_status()          # 202 = still running (2xx, won't raise)\n    time.sleep(5)                 # ~20 s typical for ~20 kb\ntranscripts = j.json()[\"data\"][\"transcripts\"]\n```\n\n## MCP workflow (handle-based)\n\nOn an MCP host, acquire a handle, then predict against it — sequences stay out of\nthe context:\n\n```\n# 1. Acquire a sequence handle (each returns a sequence_ref):\nload_demo_sequence(name=\"promoter_tp53\")  # keyless smoke test; name is required\nfetch_ensembl_sequence(gene=\"TP53\")       # gene symbol or Ensembl ID -> handle\nfetch_region(region=\"chr11:5,225,000-5,235,000\")   # coordinates -> handle\nfetch_gene_for_expression(gene=\"HBB\")     # TSS-centred 9,198 bp handle for expression\n\n# 2. Predict against the handle:\npredict_promoter(sequence_ref=\u003Cref>)\npredict_expression(sequence_ref=\u003Cref>, description=\"K562 cells\")\npredict_splice(sequence_ref=\u003Cref>)        # + predict_enhancer \u002F predict_chromatin\n\n# 3. Annotation on MCP is `find_genes` (there is no predict_annotation).\n#    It takes a handle, not a region, and runs async internally:\nfind_genes(sequence_ref=\u003Cref>)            # wait=True (default) returns the result\nfind_genes(sequence_ref=\u003Cref>, wait=False)  # -> job_id; poll get_job(job_id)\n\n# Discover models with list_models(task); reference context lives in the\n# gi:\u002F\u002Fmodels, gi:\u002F\u002Fdocs\u002Ftasks, and gi:\u002F\u002Faccount MCP resources.\n```\n\n## Composite: find genes, then predict expression\n\nTo answer \"what genes are in this region and how are they expressed?\", use the\ncomposite:\n\n- **MCP:** `find_genes_and_predict_expression(sequence_ref=..., description=...)`\n  — takes a **handle, not a region** (acquire one with `fetch_region` first);\n  `description` is required. Finds genes in the sequence and returns an\n  expression prediction for each.\n- **REST:** one call — `POST \u002Fv1\u002Fworkflows\u002Ffind-genes-and-predict-expression`,\n  body `{sequence, options}` with `sequence` 1,000–500,000 bp and\n  `options.description` (cell type \u002F assay) required; a missing or empty\n  description is a `422 validation_failed`. It annotates, centres a 9,198 bp\n  window on each discovered gene's TSS (padding with `N` up to half the window\n  rather than dropping an edge gene), and returns a prediction per gene.\n  `meta.task_specific_counts` = `{genes_found, genes_predicted, genes_skipped}`\n  with `genes_predicted + genes_skipped == genes_found`; per-gene causes in\n  `data.expression_predictions[].skip_reason`. Above **50,000 bp** (its `x-sync-limit-bp`) it forces\n  async: a synchronous request over that size is `413 sync_too_large` with\n  `error.details = {sequence_length, threshold}` — retry the same body with\n  `Prefer: respond-async`.\n\n## Errors\n\n| Code | `error.code` | Meaning | Action |\n|---|---|---|---|\n| 400 | `bad_request` | Malformed request | Check the body shape |\n| 401 \u002F 403 | `unauthorized` \u002F `forbidden` | Missing\u002Finvalid key (REST) | Set `GI_API_KEY`; or use the keyless MCP demo |\n| 404 | `not_found` | **Unknown task** (`\u002Fv1\u002Ftasks\u002Fbogus\u002Fpredict`) or unknown job | Check the task name — an unrecognised task is a 404, not a 422 |\n| 413 | `payload_too_large` | Raw request body over **16 MiB** | Split the input — this is the body cap, not the sequence cap |\n| 413 | `sync_too_large` | Synchronous request above the operation's `x-sync-limit-bp` (200,000 bp on `annotation`, 50,000 bp on the composite) | Retry with `Prefer: respond-async` |\n| 415 | `unsupported_format` | Unsupported `format` query value | Use a format the task supports; there is no silent fallback to JSON |\n| 422 | `validation_failed` | The most common failure: sequence **under the task floor or over 500,000 bp**, expression below 9,198 bp, a missing\u002Fout-of-range `tss_index`, a missing `options.description`, or **any unknown body or `options` key** | Read the message; fix the body |\n| 429 | `rate_limited` \u002F `too_many_requests` | Rate \u002F concurrency cap | Back off (honour `Retry-After`); ask GI to raise your tier |\n| 5xx | `internal_error` \u002F `service_unavailable` \u002F `model_loading` \u002F `timeout` | Server error | Retry; if persistent, contact support |\n\n`error.code` is a closed 21-value enum (`bad_request`, `unauthorized`,\n`forbidden`, `not_found`, `conflict`, `job_expired`, `payload_too_large`,\n`sync_too_large`, `unsupported_format`, `validation_failed`,\n`too_many_requests`, `rate_limited`, `internal_error`, `timeout`,\n`insufficient_memory`, `model_not_found`, `task_not_supported_by_model`,\n`model_loading`, `service_unavailable`, `http_error`, `unknown`); treat an\nunlisted value as a generic failure, not a parse error.\n\n**Branch on `code`, never on `details` or `loc`.** `details` is keyed on the\nsibling `code`; for `validation_failed` it is the `{errors: [{loc, msg, type}, …]}`\nobject the schema declares. Treat it as display-only — `code` is the stable\ndiscriminator.\n\nFor correlation, `error.request_id` and the `X-Request-Id` **header** are both\nset on every response, and success envelopes carry `meta.request_id`. Reading\nthe header first remains a safe default.\nEvery response carries `RateLimit-Limit`, `RateLimit-Remaining`,\n`RateLimit-Reset`, `RateLimit-Policy`; a `429` adds `Retry-After`.\n\n> Verified against OpenAPI `info.version` **2026.08.20.7**. The contract moves,\n> and `info.version` in `\u002Fv1\u002Fopenapi.json` reports what a given deployment\n> serves: if it is ahead of the version above, re-check the numbers in this file\n> against that document, which is the arbiter if the two disagree.\n\n## Reference files\n\n- `references\u002Ftasks.md` — per-task output shapes, model registries, the async\n  annotation contract.\n- `references\u002Fapi-and-auth.md` — REST endpoints, the `{data, meta}` envelope,\n  auth, base-URL override, tiers.\n- `references\u002Fmcp.md` — the hosted MCP tool list, the handle-based flow, and the\n  `gi:\u002F\u002F` resources.\n- `references\u002Fsequence-acquisition.md` — Ensembl fetch calls and the\n  expression-window (9,198 bp, TSS-centred) math, including `tss_index`.\n\n## Related skills\n\n- `arboreto`: Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3).\n- `tamarind`: Access a collection of open-source molecular design and structural biology tools on the Tamarind Bio platform, via its REST API or MCP serv…\n",{"name":5,"license":15,"metadata":67,"description":7,"compatibility":79},{"tags":68,"version":69,"category":70,"openclaw":71,"maintainer":76,"contributor":77,"trigger-keywords":78},"DNA language models, regulatory genomics, gene structure, sequence analysis","1.2","life-sciences",{"envVars":72,"primaryEnv":74},[73],{"name":74,"required":63,"description":75},"GI_API_KEY","Optional gi_ bearer key for the REST \u002Fv1 API and higher MCP rate and concurrency limits. The hosted MCP demo runs keyless; request a key at contact@genomicintelligence.ai.","Kalaris Labs","Genomic Intelligence","DNA sequence prediction, regulatory genomics, promoter prediction, splice site prediction, enhancer activity, chromatin state, gene expression prediction, sequence to expression, log TPM, gene annotation, transcript prediction, DNA language model, genomic intelligence, hosted inference, Ensembl sequence, FASTA prediction, cis-regulatory, TSS window, DeepSEA, DeepSTARR, BigBird splice, MCP genomics","Python 3.10+ with the `requests` library for the REST path (no dedicated SDK). Network access required. The REST `\u002Fv1` API needs a `GI_API_KEY` (a `gi_` bearer); the hosted MCP server at mcp.genomicintelligence.ai\u002Fmcp works keyless against a rate- and concurrency-limited public demo tier, key optional.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fgenomic-intelligence",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":91,"prompt":101,"zipAvailable":102},[92,95,98],{"tool":93,"command":94},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill genomic-intelligence",{"tool":96,"command":97},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill genomic-intelligence",{"tool":99,"command":100},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill genomic-intelligence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fgenomic-intelligence\u002FSKILL.md",true,[104,110,114,118],{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fapi-and-auth.md","REFERENCE","参考文档",5243,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fgenomic-intelligence\u002Freferences\u002Fapi-and-auth.md",{"path":111,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fmcp.md",3949,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fgenomic-intelligence\u002Freferences\u002Fmcp.md",{"path":115,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fsequence-acquisition.md",3410,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fgenomic-intelligence\u002Freferences\u002Fsequence-acquisition.md",{"path":119,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Ftasks.md",11734,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fgenomic-intelligence\u002Freferences\u002Ftasks.md",[123,132,140,148,156,164],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":131},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":131},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":131},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":131},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":131},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":131},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]