boltz-small-molecule-adme
Predict Tier-1 ADME/ADMET for small molecules with Boltz from bare SMILES — no target, no docking. Use when the user wants solubility, permeability, or lipophilicity/logD for a molecule or list of molecules. Not for ranking molecules against a protein target (use boltz-small-molecule-screen, which already returns ADME free).
- License 许可
- MIT
- 最近更新
- 2026-07-19
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- boltz-small-molecule-adme
- description
- Predict Tier-1 ADME/ADMET for small molecules with Boltz from bare SMILES — no target, no docking. Use when the user wants solubility, permeability, or lipophilicity/logD for a molecule or list of molecules. Not for ranking molecules against a protein target (use boltz-small-molecule-screen, which already returns ADME free).
02 资源文件 3
- 参考文档agents/openai.yaml258 B
- 参考文档references/api.md4.5 KB
- 参考文档references/results.md2.1 KB
03 SKILL.md 正文
Workflow
If boltz-api is missing from PATH, use boltz-cli-setup for install/update guidance before retrying.
If a command reports missing or expired authentication, use boltz-cli-setup to start boltz-api auth login --device-code before retrying; do not ask permission first.
If the agent host sandbox blocks boltz-api install/auth/API calls, use boltz-cli-setup to request the host sandbox bypass/escalation needed for user-wide CLI install, browser login, credential storage, temp files, or API access before retrying.
Use this skill for standalone ADME triage on SMILES the user already has. No protein target is involved. If the user is also screening or docking those molecules against a target, prefer boltz-small-molecule-screen — it returns the same ADME block free as part of the screen.
- Normalize the molecules from raw SMILES, a CSV (auto-detect the SMILES column),
.smi, or.txtinto themoleculeslist. Each entry is{smiles, id?}; the optionalidis echoed back asexternal_idon each result so you can map results to inputs. - Hard cap: 128 molecules per request. If the list exceeds 128, split into batches of ≤128 and submit one request per batch (suffix the run name, for example
-b1,-b2), then merge results. Never send more than 128 in one call — the API rejects it withVALIDATION_ERROR: input.molecules must contain at most 128 items. - Author the payload YAML or JSON, run
estimate-cost, show the USD cost, wait for explicit confirmation. ADME is priced at $0.01 per molecule (size-independent);estimate-costreturns the authoritative total — always quote it. runto submit and wait — ADME finishes in seconds, so it is synchronous and needs no background polling.runpersists results locally under--root-dir/<run-name>/.- Report from
<output-root>/<run-name>/run.json→output.molecules[]. For each molecule showexternal_id(orsmiles),solubility,permeability, andlipophilicity. The three values live under each molecule'sadmeobject. Call out any molecule withstatus: failedand itserror(an object{code, message}, e.g. codeadme_enumeration_failed, messageInvalid SMILES) —admeisnullthere; one bad SMILES fails only that molecule, not the batch. Read references/results.md for the output layout and references/api.md for the payload and batching details.
ADME values are approximate estimates for triage and ranking, not absolute measurements.
Command Pattern
# Replace placeholders with concrete absolute paths before running.
# Use a short descriptive run name, for example: adme-<library>-v1
boltz-api predictions:adme estimate-cost \
--model adme-v1 --input @yaml:///absolute/path/payload.yaml
# `run` is synchronous (submit + wait + persist) and finishes in seconds — no background mode needed.
# Claude Code: run as a normal Bash command. Codex: run as a foreground shell command; if Codex
# returns a session_id because it is still running, poll it. Do not append "&" or use nohup in Codex.
boltz-api predictions:adme run \
--model adme-v1 \
--idempotency-key "<run-name>" \
--input @yaml:///absolute/path/payload.yaml \
--name "<run-name>" \
--root-dir "/absolute/path/boltz-experiments" \
--poll-interval-seconds 5
# -> /absolute/path/boltz-experiments/<run-name>/run.json (output.molecules[].adme)
Payload is just a molecules list — the API body field name, not the direct CLI flag. --model adme-v1 is required.
Always Do This
- Keep payload field names exactly as the API body names shown in
references/api.md(molecules, each{smiles, id?}). - Pass
--model adme-v1on everyestimate-cost,run, andstart. - Enforce the 128-molecule-per-request cap. Chunk larger libraries into ≤128 batches and submit each as its own run; merge the per-batch
run.jsonoutputs when reporting. - Use absolute paths for the output root and payload files. Do not
cdinto the run directory; pass the same--root-dirand use absolute paths so later relative paths do not drift. - Prefer one merged top-level payload via
--input @yaml:///absolute/path/payload.yamlor@json:///absolute/path/payload.json. Keep--model,--idempotency-key, and--workspace-idtop-level. Never use@file://or@./. - Run
estimate-costand show the USD total before submitting. ADME is $0.01/molecule (size-independent);estimate-costreturns the authoritative total — always use it. - Use the same slug as both
--idempotency-keyand--nameso re-runs resume via.boltz-run.json. - In permission-gated agents such as Claude Code, keep each Boltz call as a top-level command that starts with
boltz-api. Prefer concrete arguments oversh -c, inline environment assignments, aliases, wrapper scripts, loops, or pipelines unless the user already allowed that exact command form. - ADME
runis synchronous and finishes in seconds, so unlike the screen/design endpoints it needs no background/non-blocking mode. In Claude Code, run it as a normal Bash call. In Codex, run it as a foreground shell command; if Codex returns asession_idbecause the command is still running, poll it. Do not append&or usenohupin Codex. - Do not require or accept a protein target — ADME is structure-free. If the user wants ADME and binding against a target, redirect to
boltz-small-molecule-screen.
Escape Hatch
- Payload reference: https://api.boltz.bio/docs/api/resources/predictions/subresources/adme/methods/start/
- Guide: https://api.boltz.bio/docs/guides/small-molecule-adme/
- CLI flag names:
boltz-api predictions:adme run --help
Read references/api.md for the molecules payload shape, the per-molecule output fields, the 128-molecule cap, and error handling.
Outputs
Read <output-root>/<run-name>/run.json and report output.molecules[]. There are no structure files — ADME returns scalar/categorical values only. Read references/results.md for the local layout and per-molecule output fields; references/api.md has the full request/response schema.
04 同仓库更多 Skills
Zotero
Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.
zoom-apps-sdk
Use when using Apps SDK.
youtube
Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".
yeet
Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.
x-post-creator
Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.
x-api
Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".