[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CGCST693SHPXWN48VXG6Z3":3,"skill-same:01M7CGCST693SHPXWN48VXG6Z3":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":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CGCST693SHPXWN48VXG6Z3","boltz-structure-and-binding",null,"Predict structures and binding for one defined complex with Boltz. Use when folding a protein, RNA, DNA, or ligand complex, docking one ligand, predicting an interface, or scoring binding. Not for screening libraries or design.","rossboyd\u002Fquickque","rossboyd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3195729?v=4","01M7CG99NTNRFV0TWTZX9JY9CQ","rbyd","01M7CG99PH4WEP5P45VTBNPDB0",0,"MIT","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fboltz-api-cli\u002Fskills\u002Fboltz-structure-and-binding\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: boltz-structure-and-binding\ndescription: Predict structures and binding for one defined complex with Boltz. Use when folding a protein, RNA, DNA, or ligand complex, docking one ligand, predicting an interface, or scoring binding. Not for screening libraries or design.\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 one defined complex, not a library workflow.\n\n1. Normalize the inputs into `entities`. Each entity is **`{type, chain_ids, value}`** — note plural `chain_ids` (an array, even for one chain) and the field is `value`, **not** `sequence`:\n\n   ```json\n   {\"entities\": [{\"type\": \"protein\", \"chain_ids\": [\"A\"], \"value\": \"MKTAYIAKQRQISFVKSHFSRQ\"}]}\n   ```\n\n   `type` is one of `protein | rna | dna | ligand_smiles | ligand_ccd`. Chain IDs go in entity order (`A`, `B`, `C`, …) unless the user specifies otherwise. Read `references\u002Fapi.md` for per-type field variants (`cyclic`, `modifications`, ligand CCD codes, etc.) **before** authoring your first payload — agent guesses like `sequence:` or `chain_id: \"A\"` (singular) fail with unclear 400 errors.\n2. If the user wants binding metrics, add a flat `binding` block with an explicit `type` field. For ligand-protein binding use:\n\n   ```yaml\n   binding:\n     type: ligand_protein_binding\n     binder_chain_id: B\n   ```\n\n   For protein-protein binding use:\n\n   ```yaml\n   binding:\n     type: protein_protein_binding\n     binder_chain_ids: [B]\n   ```\n\n   Do not nest the variant name under `binding` (for example, no `binding.ligand_protein_binding` object).\n3. Supported optional features include `constraints`, `bonds`, `modifications`, `model_options`, and binding metrics; only add them if the user asks. Read [references\u002Fapi.md](references\u002Fapi.md) for exact shapes and examples.\n4. Author the payload YAML or JSON, run `estimate-cost`, show the USD cost, wait for explicit confirmation.\n5. `start` to submit (synchronous). Capture the ID.\n6. Launch `download-results` with the agent runtime's background\u002Fnon-blocking command facility so polling + download continue without blocking the agent session. In Claude Code, use Bash with `run_in_background: true`. In Codex, run `download-results` as a foreground shell command with `yield_time_ms: 1000`; if Codex returns a `session_id`, keep it for optional same-thread polling, but treat `download-status` plus the run directory as the durable source of truth. In Codex app\u002Fdesktop runtimes that expose same-thread heartbeat automations, create a heartbeat that checks `download-status` periodically and posts a concise completion or failure update when the download reaches a terminal state. After launching the downloader, always report the job ID, run name, and output directory. Include the next check cadence if the heartbeat was created; otherwise include the `download-status` command.\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: sab-\u003Ctarget>-\u003Cligand>-v1\n\n# 1. estimate\nboltz-api predictions:structure-and-binding estimate-cost \\\n  --model boltz-2.1 \\\n  --input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml\n\n# 2. confirm with user, then submit\nboltz-api predictions:structure-and-binding start \\\n       --model boltz-2.1 \\\n       --idempotency-key \"\u003Crun-name>\" \\\n       --input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml \\\n       --raw-output --transform id\n\n# 3. Copy the printed job ID into this command, then launch it in the agent\n# runtime's background\u002Fnon-blocking mode.\n# Claude Code: Bash with run_in_background=true.\n# Codex: foreground shell command with yield_time_ms=1000; keep the returned session_id if one is provided.\n# Do not append \"&\" or use nohup in Codex.\nboltz-api download-results \\\n  --id \"\u003Cjob-id-from-start>\" --name \"\u003Crun-name>\" \\\n  --root-dir \"\u002Fabsolute\u002Fpath\u002Fboltz-experiments\" \\\n  --poll-interval-seconds 10\n# -> \u002Fabsolute\u002Fpath\u002Fboltz-experiments\u002F\u003Crun-name>\u002Foutputs\u002Farchive.tar.gz, .boltz-run.json\n```\n\n## Always Do This\n\n- Keep payload field names exactly as the API body names shown in `references\u002Fapi.md`; then pass the merged payload with `--input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml` or `@json:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.json`. Never use `@.\u002Fpayload.yaml` or `@file:\u002F\u002F` for object-typed payloads.\n- Use absolute paths for the output root, payload files, and embedded structure files. Do not `cd` into the run directory for follow-up commands; pass the same `--root-dir` and use absolute paths so later relative paths do not drift.\n- Residue indices are 0-based wherever the payload asks for residue positions (constraints, modifications, contact tokens).\n- For CIF\u002FPDB bytes embedded in `--target` \u002F `structure.data`, use `@data:\u002F\u002F\u002Fabsolute\u002Fpath\u002Ffile.cif` — it detects binary and base64-encodes. Don't use bare `@path` for binary data.\n- Use the same slug as both `--idempotency-key` at submit time and `--name` at download time so re-runs are idempotent and resume from `.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 around the `boltz-api` invocation unless the user already allowed that exact command form. Use `--raw-output --transform id`, read the printed ID, then paste that literal ID into the next `download-results` command.\n- Prefer the agent runtime's background\u002Fnon-blocking command mode for `download-results`. In Codex specifically, keep `download-results` in the foreground and set the shell tool yield to 1000 ms; Codex will return a `session_id` if the command is still running. Do not append `&` or use `nohup` in Codex because the tool runner may clean up shell-backgrounded descendants before `.boltz-run.json` is fully written.\n- After the background\u002Fsession starts, do not manually wait on it or run ad hoc polling loops. `download-results` emits JSONL progress on stderr by default; add `--progress-format text --verbose` only when you explicitly want human-readable logs.\n- In Codex app\u002Fdesktop runtimes with same-thread heartbeat automation support, schedule a heartbeat after launching `download-results`. The heartbeat should run `boltz-api --format json download-status --name \"\u003Crun-name>\" --root-dir \"\u002Fabsolute\u002Fpath\u002Fboltz-experiments\"` on a sensible cadence, post only material status changes or terminal completion\u002Ffailure, and stop once terminal. Poll the saved `session_id` with an empty `write_stdin` only for interactive, user-requested progress checks. Do not loop `retrieve` yourself.\n- If the current host has no heartbeat automation support, do not claim an automatic next check. Report the job ID, run name, output directory, and the command needed to check `download-status`.\n- If detached download needs to be restarted, re-run `boltz-api download-results` with the same `--name \"\u003Crun-name>\"` and the same `--root-dir`.\n- Poll interval: keep `--poll-interval-seconds 10` for SAB — predictions usually finish in under a few minutes.\n- Cost: there is no published per-unit rate to cite for SAB — run `estimate-cost` and state only the figure it returns. Don't estimate or comment on cost.\n\n## Escape Hatch\n\nFor anything not covered in `references\u002Fapi.md`:\n\n- Payload reference: \u003Chttps:\u002F\u002Fapi.boltz.bio\u002Fdocs\u002Fapi\u002Fpython\u002Fresources\u002Fpredictions\u002Fsubresources\u002Fstructure_and_binding\u002Fmethods\u002Fstart>\n- CLI flag names: `boltz-api predictions:structure-and-binding start --help` (schema details aren't there — just flag names and types)\n\nRead [references\u002Fapi.md](references\u002Fapi.md) for entity shapes, binding variants, bonds, constraints, model options, and input examples. Read [references\u002Fresults.md](references\u002Fresults.md) when summarizing downloaded outputs, metrics, or validation quirks.\n\n## Outputs\n\nSummarize `metrics.json` and point the user at the downloaded CIF path. Read [references\u002Fresults.md](references\u002Fresults.md) for the local layout, nested metrics, binding metric variants, and SAB validation quirks.\n\n## SAB 400 validation quirk\n\nIf the server rejects a payload with only `{\"code\":\"VALIDATION_ERROR\",\"message\":\"Request validation failed\"}`, inspect `entities`, `binding`, and `constraints`; read [references\u002Fresults.md](references\u002Fresults.md) for details.\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 one defined complex, not a library workflow.\n\n1. Normalize the inputs into `entities`. Each entity is **`{type, chain_ids, value}`** — note plural `chain_ids` (an array, even for one chain) and the field is `value`, **not** `sequence`:\n\n   ```json\n   {\"entities\": [{\"type\": \"protein\", \"chain_ids\": [\"A\"], \"value\": \"MKTAYIAKQRQISFVKSHFSRQ\"}]}\n   ```\n\n   `type` is one of `protein | rna | dna | ligand_smiles | ligand_ccd`. Chain IDs go in entity order (`A`, `B`, `C`, …) unless the user specifies otherwise. Read `references\u002Fapi.md` for per-type field variants (`cyclic`, `modifications`, ligand CCD codes, etc.) **before** authoring your first payload — agent guesses like `sequence:` or `chain_id: \"A\"` (singular) fail with unclear 400 errors.\n2. If the user wants binding metrics, add a flat `binding` block with an explicit `type` field. For ligand-protein binding use:\n\n   ```yaml\n   binding:\n     type: ligand_protein_binding\n     binder_chain_id: B\n   ```\n\n   For protein-protein binding use:\n\n   ```yaml\n   binding:\n     type: protein_protein_binding\n     binder_chain_ids: [B]\n   ```\n\n   Do not nest the variant name under `binding` (for example, no `binding.ligand_protein_binding` object).\n3. Supported optional features include `constraints`, `bonds`, `modifications`, `model_options`, and binding metrics; only add them if the user asks. Read [references\u002Fapi.md](references\u002Fapi.md) for exact shapes and examples.\n4. Author the payload YAML or JSON, run `estimate-cost`, show the USD cost, wait for explicit confirmation.\n5. `start` to submit (synchronous). Capture the ID.\n6. Launch `download-results` with the agent runtime's background\u002Fnon-blocking command facility so polling + download continue without blocking the agent session. In Claude Code, use Bash with `run_in_background: true`. In Codex, run `download-results` as a foreground shell command with `yield_time_ms: 1000`; if Codex returns a `session_id`, keep it for optional same-thread polling, but treat `download-status` plus the run directory as the durable source of truth. In Codex app\u002Fdesktop runtimes that expose same-thread heartbeat automations, create a heartbeat that checks `download-status` periodically and posts a concise completion or failure update when the download reaches a terminal state. After launching the downloader, always report the job ID, run name, and output directory. Include the next check cadence if the heartbeat was created; otherwise include the `download-status` command.\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: sab-\u003Ctarget>-\u003Cligand>-v1\n\n# 1. estimate\nboltz-api predictions:structure-and-binding estimate-cost \\\n  --model boltz-2.1 \\\n  --input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml\n\n# 2. confirm with user, then submit\nboltz-api predictions:structure-and-binding start \\\n       --model boltz-2.1 \\\n       --idempotency-key \"\u003Crun-name>\" \\\n       --input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml \\\n       --raw-output --transform id\n\n# 3. Copy the printed job ID into this command, then launch it in the agent\n# runtime's background\u002Fnon-blocking mode.\n# Claude Code: Bash with run_in_background=true.\n# Codex: foreground shell command with yield_time_ms=1000; keep the returned session_id if one is provided.\n# Do not append \"&\" or use nohup in Codex.\nboltz-api download-results \\\n  --id \"\u003Cjob-id-from-start>\" --name \"\u003Crun-name>\" \\\n  --root-dir \"\u002Fabsolute\u002Fpath\u002Fboltz-experiments\" \\\n  --poll-interval-seconds 10\n# -> \u002Fabsolute\u002Fpath\u002Fboltz-experiments\u002F\u003Crun-name>\u002Foutputs\u002Farchive.tar.gz, .boltz-run.json\n```\n\n## Always Do This\n\n- Keep payload field names exactly as the API body names shown in `references\u002Fapi.md`; then pass the merged payload with `--input @yaml:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.yaml` or `@json:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fpayload.json`. Never use `@.\u002Fpayload.yaml` or `@file:\u002F\u002F` for object-typed payloads.\n- Use absolute paths for the output root, payload files, and embedded structure files. Do not `cd` into the run directory for follow-up commands; pass the same `--root-dir` and use absolute paths so later relative paths do not drift.\n- Residue indices are 0-based wherever the payload asks for residue positions (constraints, modifications, contact tokens).\n- For CIF\u002FPDB bytes embedded in `--target` \u002F `structure.data`, use `@data:\u002F\u002F\u002Fabsolute\u002Fpath\u002Ffile.cif` — it detects binary and base64-encodes. Don't use bare `@path` for binary data.\n- Use the same slug as both `--idempotency-key` at submit time and `--name` at download time so re-runs are idempotent and resume from `.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 around the `boltz-api` invocation unless the user already allowed that exact command form. Use `--raw-output --transform id`, read the printed ID, then paste that literal ID into the next `download-results` command.\n- Prefer the agent runtime's background\u002Fnon-blocking command mode for `download-results`. In Codex specifically, keep `download-results` in the foreground and set the shell tool yield to 1000 ms; Codex will return a `session_id` if the command is still running. Do not append `&` or use `nohup` in Codex because the tool runner may clean up shell-backgrounded descendants before `.boltz-run.json` is fully written.\n- After the background\u002Fsession starts, do not manually wait on it or run ad hoc polling loops. `download-results` emits JSONL progress on stderr by default; add `--progress-format text --verbose` only when you explicitly want human-readable logs.\n- In Codex app\u002Fdesktop runtimes with same-thread heartbeat automation support, schedule a heartbeat after launching `download-results`. The heartbeat should run `boltz-api --format json download-status --name \"\u003Crun-name>\" --root-dir \"\u002Fabsolute\u002Fpath\u002Fboltz-experiments\"` on a sensible cadence, post only material status changes or terminal completion\u002Ffailure, and stop once terminal. Poll the saved `session_id` with an empty `write_stdin` only for interactive, user-requested progress checks. Do not loop `retrieve` yourself.\n- If the current host has no heartbeat automation support, do not claim an automatic next check. Report the job ID, run name, output directory, and the command needed to check `download-status`.\n- If detached download needs to be restarted, re-run `boltz-api download-results` with the same `--name \"\u003Crun-name>\"` and the same `--root-dir`.\n- Poll interval: keep `--poll-interval-seconds 10` for SAB — predictions usually finish in under a few minutes.\n- Cost: there is no published per-unit rate to cite for SAB — run `estimate-cost` and state only the figure it returns. Don't estimate or comment on cost.\n\n## Escape Hatch\n\nFor anything not covered in `references\u002Fapi.md`:\n\n- Payload reference: \u003Chttps:\u002F\u002Fapi.boltz.bio\u002Fdocs\u002Fapi\u002Fpython\u002Fresources\u002Fpredictions\u002Fsubresources\u002Fstructure_and_binding\u002Fmethods\u002Fstart>\n- CLI flag names: `boltz-api predictions:structure-and-binding start --help` (schema details aren't there — just flag names and types)\n\nRead [references\u002Fapi.md](references\u002Fapi.md) for entity shapes, binding variants, bonds, constraints, model options, and input examples. Read [references\u002Fresults.md](references\u002Fresults.md) when summarizing downloaded outputs, metrics, or validation quirks.\n\n## Outputs\n\nSummarize `metrics.json` and point the user at the downloaded CIF path. Read [references\u002Fresults.md](references\u002Fresults.md) for the local layout, nested metrics, binding metric variants, and SAB validation quirks.\n\n## SAB 400 validation quirk\n\nIf the server rejects a payload with only `{\"code\":\"VALIDATION_ERROR\",\"message\":\"Request validation failed\"}`, inspect `entities`, `binding`, and `constraints`; read [references\u002Fresults.md](references\u002Fresults.md) for details.\n",{"name":5,"description":7},"main","907b1d897cc6743f7f133f8ea2021e1331b0b020",".codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fboltz-api-cli\u002Fskills\u002Fboltz-structure-and-binding","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque","https:\u002F\u002Fgithub.com\u002Frossboyd","www.bigideasgroup.co.uk","2026-09-22 02:03:50",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add rossboyd\u002Fquickque --skill boltz-structure-and-binding",{"tool":37,"command":38},"bunx","bunx skills add rossboyd\u002Fquickque --skill boltz-structure-and-binding",{"tool":40,"command":41},"pnpm","pnpm dlx skills add rossboyd\u002Fquickque --skill boltz-structure-and-binding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fboltz-api-cli\u002Fskills\u002Fboltz-structure-and-binding\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",243,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fboltz-api-cli\u002Fskills\u002Fboltz-structure-and-binding\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fapi.md",9831,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fboltz-api-cli\u002Fskills\u002Fboltz-structure-and-binding\u002Freferences\u002Fapi.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fresults.md",1637,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fboltz-api-cli\u002Fskills\u002Fboltz-structure-and-binding\u002Freferences\u002Fresults.md",[60,69,77,84,91,99],{"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":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CJSS21K09H3ZQZMPFR4ZAG","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-installer\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CJSM1F4E7RBXCS3C18EFBY","skill-creator","Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CJSGF2PJM504Q6TZCNT27C","review-agent","Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Freview-agent\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CJSBQTPFEQYZF4VWS7QZ3N","plugin-creator","Create and scaffold plugin directories for Codex with a required `.codex-plugin\u002Fplugin.json`, optional plugin folders\u002Ffiles, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CJS5BHJZKA16353PVZGC50","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7CJRY1FC048P3RF4YQZ6J8B","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fimagegen\u002FSKILL.md",[],[]]