[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79D0QA2DJ569BPEK080KMMK":3,"skill-same:01M79D0QA2DJ569BPEK080KMMK":59},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79D0QA2DJ569BPEK080KMMK","boltz-small-molecule-adme",null,"Predict Tier-1 ADME\u002FADMET for small molecules with Boltz from bare SMILES — no target, no docking. Use when the user wants solubility, permeability, or lipophilicity\u002FlogD 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).","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboltz-small-molecule-adme\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: boltz-small-molecule-adme\ndescription: Predict Tier-1 ADME\u002FADMET for small molecules with Boltz from bare SMILES — no target, no docking. Use when the user wants solubility, permeability, or lipophilicity\u002FlogD 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).\n---\n\n## Workflow\n\nIf `boltz-api` is missing from `PATH`, use `boltz-cli-setup` for install\u002Fupdate guidance before retrying.\nIf 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.\nIf the agent host sandbox blocks `boltz-api` install\u002Fauth\u002FAPI calls, use `boltz-cli-setup` to request the host sandbox bypass\u002Fescalation needed for user-wide CLI install, browser login, credential storage, temp files, or API access before retrying.\n\nUse 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.\n\n1. Normalize the molecules from raw SMILES, a CSV (auto-detect the SMILES column), `.smi`, or `.txt` into the `molecules` list. Each entry is `{smiles, id?}`; the optional `id` is echoed back as `external_id` on each result so you can map results to inputs.\n2. **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 with `VALIDATION_ERROR: input.molecules must contain at most 128 items`.\n3. 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-cost` returns the authoritative total — always quote it.\n4. `run` to submit and wait — ADME finishes in seconds, so it is synchronous and needs no background polling. `run` persists results locally under `--root-dir\u002F\u003Crun-name>\u002F`.\n5. Report from `\u003Coutput-root>\u002F\u003Crun-name>\u002Frun.json` → `output.molecules[]`. For each molecule show `external_id` (or `smiles`), `solubility`, `permeability`, and `lipophilicity`. The three values live under each molecule's `adme` object. Call out any molecule with `status: failed` and its `error` (an object `{code, message}`, e.g. code `adme_enumeration_failed`, message `Invalid SMILES`) — `adme` is `null` there; one bad SMILES fails only that molecule, not the batch. Read [references\u002Fresults.md](references\u002Fresults.md) for the output layout and [references\u002Fapi.md](references\u002Fapi.md) for the payload and batching details.\n\nADME values are approximate estimates for triage and ranking, not absolute measurements.\n\n## Command Pattern\n\n```bash\n# Replace placeholders with concrete absolute paths before running.\n# Use a short descriptive run name, for example: adme-\u003Clibrary>-v1\n\nboltz-api predictions:adme estimate-cost \\\n  --model adme-v1 --input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml\n\n# `run` is synchronous (submit + wait + persist) and finishes in seconds — no background mode needed.\n# Claude Code: run as a normal Bash command. Codex: run as a foreground shell command; if Codex\n# returns a session_id because it is still running, poll it. Do not append \"&\" or use nohup in Codex.\nboltz-api predictions:adme run \\\n  --model adme-v1 \\\n  --idempotency-key \"\u003Crun-name>\" \\\n  --input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml \\\n  --name \"\u003Crun-name>\" \\\n  --root-dir \"\u002Fabsolute\u002Fpath\u002Fboltz-experiments\" \\\n  --poll-interval-seconds 5\n# -> \u002Fabsolute\u002Fpath\u002Fboltz-experiments\u002F\u003Crun-name>\u002Frun.json  (output.molecules[].adme)\n```\n\nPayload is just a `molecules` list — the API body field name, not the direct CLI flag. `--model adme-v1` is required.\n\n## Always Do This\n\n- Keep payload field names exactly as the API body names shown in `references\u002Fapi.md` (`molecules`, each `{smiles, id?}`).\n- Pass `--model adme-v1` on every `estimate-cost`, `run`, and `start`.\n- 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.json` outputs when reporting.\n- Use absolute paths for the output root and payload files. Do not `cd` into the run directory; pass the same `--root-dir` and use absolute paths so later relative paths do not drift.\n- Prefer one merged top-level payload via `--input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml` or `@json:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.json`. Keep `--model`, `--idempotency-key`, and `--workspace-id` top-level. Never use `@file:\u002F\u002F` or `@.\u002F`.\n- Run `estimate-cost` and show the USD total before submitting. ADME is $0.01\u002Fmolecule (size-independent); `estimate-cost` returns the authoritative total — always use it.\n- Use the same slug as both `--idempotency-key` and `--name` so re-runs resume via `.boltz-run.json`.\n- 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 over `sh -c`, inline environment assignments, aliases, wrapper scripts, loops, or pipelines unless the user already allowed that exact command form.\n- ADME `run` is synchronous and finishes in seconds, so unlike the screen\u002Fdesign endpoints it needs no background\u002Fnon-blocking mode. In Claude Code, run it as a normal Bash call. In Codex, run it as a foreground shell command; if Codex returns a `session_id` because the command is still running, poll it. Do not append `&` or use `nohup` in Codex.\n- 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`.\n\n## Escape Hatch\n\n- Payload reference: \u003Chttps:\u002F\u002Fapi.boltz.bio\u002Fdocs\u002Fapi\u002Fresources\u002Fpredictions\u002Fsubresources\u002Fadme\u002Fmethods\u002Fstart\u002F>\n- Guide: \u003Chttps:\u002F\u002Fapi.boltz.bio\u002Fdocs\u002Fguides\u002Fsmall-molecule-adme\u002F>\n- CLI flag names: `boltz-api predictions:adme run --help`\n\nRead [references\u002Fapi.md](references\u002Fapi.md) for the `molecules` payload shape, the per-molecule output fields, the 128-molecule cap, and error handling.\n\n## Outputs\n\nRead `\u003Coutput-root>\u002F\u003Crun-name>\u002Frun.json` and report `output.molecules[]`. There are no structure files — ADME returns scalar\u002Fcategorical values only. Read [references\u002Fresults.md](references\u002Fresults.md) for the local layout and per-molecule output fields; [references\u002Fapi.md](references\u002Fapi.md) has the full request\u002Fresponse schema.\n","## Workflow\n\nIf `boltz-api` is missing from `PATH`, use `boltz-cli-setup` for install\u002Fupdate guidance before retrying.\nIf 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.\nIf the agent host sandbox blocks `boltz-api` install\u002Fauth\u002FAPI calls, use `boltz-cli-setup` to request the host sandbox bypass\u002Fescalation needed for user-wide CLI install, browser login, credential storage, temp files, or API access before retrying.\n\nUse 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.\n\n1. Normalize the molecules from raw SMILES, a CSV (auto-detect the SMILES column), `.smi`, or `.txt` into the `molecules` list. Each entry is `{smiles, id?}`; the optional `id` is echoed back as `external_id` on each result so you can map results to inputs.\n2. **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 with `VALIDATION_ERROR: input.molecules must contain at most 128 items`.\n3. 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-cost` returns the authoritative total — always quote it.\n4. `run` to submit and wait — ADME finishes in seconds, so it is synchronous and needs no background polling. `run` persists results locally under `--root-dir\u002F\u003Crun-name>\u002F`.\n5. Report from `\u003Coutput-root>\u002F\u003Crun-name>\u002Frun.json` → `output.molecules[]`. For each molecule show `external_id` (or `smiles`), `solubility`, `permeability`, and `lipophilicity`. The three values live under each molecule's `adme` object. Call out any molecule with `status: failed` and its `error` (an object `{code, message}`, e.g. code `adme_enumeration_failed`, message `Invalid SMILES`) — `adme` is `null` there; one bad SMILES fails only that molecule, not the batch. Read [references\u002Fresults.md](references\u002Fresults.md) for the output layout and [references\u002Fapi.md](references\u002Fapi.md) for the payload and batching details.\n\nADME values are approximate estimates for triage and ranking, not absolute measurements.\n\n## Command Pattern\n\n```bash\n# Replace placeholders with concrete absolute paths before running.\n# Use a short descriptive run name, for example: adme-\u003Clibrary>-v1\n\nboltz-api predictions:adme estimate-cost \\\n  --model adme-v1 --input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml\n\n# `run` is synchronous (submit + wait + persist) and finishes in seconds — no background mode needed.\n# Claude Code: run as a normal Bash command. Codex: run as a foreground shell command; if Codex\n# returns a session_id because it is still running, poll it. Do not append \"&\" or use nohup in Codex.\nboltz-api predictions:adme run \\\n  --model adme-v1 \\\n  --idempotency-key \"\u003Crun-name>\" \\\n  --input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml \\\n  --name \"\u003Crun-name>\" \\\n  --root-dir \"\u002Fabsolute\u002Fpath\u002Fboltz-experiments\" \\\n  --poll-interval-seconds 5\n# -> \u002Fabsolute\u002Fpath\u002Fboltz-experiments\u002F\u003Crun-name>\u002Frun.json  (output.molecules[].adme)\n```\n\nPayload is just a `molecules` list — the API body field name, not the direct CLI flag. `--model adme-v1` is required.\n\n## Always Do This\n\n- Keep payload field names exactly as the API body names shown in `references\u002Fapi.md` (`molecules`, each `{smiles, id?}`).\n- Pass `--model adme-v1` on every `estimate-cost`, `run`, and `start`.\n- 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.json` outputs when reporting.\n- Use absolute paths for the output root and payload files. Do not `cd` into the run directory; pass the same `--root-dir` and use absolute paths so later relative paths do not drift.\n- Prefer one merged top-level payload via `--input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml` or `@json:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.json`. Keep `--model`, `--idempotency-key`, and `--workspace-id` top-level. Never use `@file:\u002F\u002F` or `@.\u002F`.\n- Run `estimate-cost` and show the USD total before submitting. ADME is $0.01\u002Fmolecule (size-independent); `estimate-cost` returns the authoritative total — always use it.\n- Use the same slug as both `--idempotency-key` and `--name` so re-runs resume via `.boltz-run.json`.\n- 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 over `sh -c`, inline environment assignments, aliases, wrapper scripts, loops, or pipelines unless the user already allowed that exact command form.\n- ADME `run` is synchronous and finishes in seconds, so unlike the screen\u002Fdesign endpoints it needs no background\u002Fnon-blocking mode. In Claude Code, run it as a normal Bash call. In Codex, run it as a foreground shell command; if Codex returns a `session_id` because the command is still running, poll it. Do not append `&` or use `nohup` in Codex.\n- 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`.\n\n## Escape Hatch\n\n- Payload reference: \u003Chttps:\u002F\u002Fapi.boltz.bio\u002Fdocs\u002Fapi\u002Fresources\u002Fpredictions\u002Fsubresources\u002Fadme\u002Fmethods\u002Fstart\u002F>\n- Guide: \u003Chttps:\u002F\u002Fapi.boltz.bio\u002Fdocs\u002Fguides\u002Fsmall-molecule-adme\u002F>\n- CLI flag names: `boltz-api predictions:adme run --help`\n\nRead [references\u002Fapi.md](references\u002Fapi.md) for the `molecules` payload shape, the per-molecule output fields, the 128-molecule cap, and error handling.\n\n## Outputs\n\nRead `\u003Coutput-root>\u002F\u003Crun-name>\u002Frun.json` and report `output.molecules[]`. There are no structure files — ADME returns scalar\u002Fcategorical values only. Read [references\u002Fresults.md](references\u002Fresults.md) for the local layout and per-molecule output fields; [references\u002Fapi.md](references\u002Fapi.md) has the full request\u002Fresponse schema.\n",{"name":5,"description":7},"main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fboltz-small-molecule-adme","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zfifteen\u002Fskills-catalog --skill boltz-small-molecule-adme",{"tool":37,"command":38},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill boltz-small-molecule-adme",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill boltz-small-molecule-adme","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboltz-small-molecule-adme\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",258,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboltz-small-molecule-adme\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fapi.md",4616,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboltz-small-molecule-adme\u002Freferences\u002Fapi.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fresults.md",2182,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fboltz-small-molecule-adme\u002Freferences\u002Fresults.md",[60,67,74,81,90,97],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS 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.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","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:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","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, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","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\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]