back
loading skill details...
Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user…
CLI Creator Create a real CLI that future Codex threads can run by command name from any working directory. This skill is for durable tools, not one-off scripts. If a short script in the current repo solves the task, write the script there instead. Start Name the target tool, its source, and the first real jobs it should do: Source: API docs, OpenAPI JSON, SDK docs, curl examples, browser app, existing internal script, article, or working shell history. Jobs: literal reads/writes such as list drafts, download failed job logs, search messages, upload media, read queue schedule. Install name: a short binary name such as ci-logs, slack-cli, sentry-cli, or buildkite-logs. Prefer a new folder under ~/code/clis/<tool-name> when the user wants a personal tool and has not named a repo. Before scaffolding, check whether the proposed command already exists:
don't have the plugin yet? install it then click "run inline in claude" again.