Agent skill · software engineering · openai
cli-creator
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 wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.
Why this skill is useful
Adds a complete CLI scaffolding script that integrates with various sources and manages authentication, which the AI cannot generate on its own.
What it needs
Requires cargo, node, python3 installed locally. About 6k tokens when loaded. Last updated 2026-07-14. 24,594 stars on the source repository.
What this skill does
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: If it exists, choose a clearer install name or ask the user. Choose the Runtime Before choosing, inspect the user's machine and source material: Then choose the least surprising toolchain: Default to Rust for a durable CLI Codex should run from any repo: one fast binary, strong argument parsing, good JSON handling, easy copy/install into ~/.local/bin. Use TypeScript/Node when the official SDK, auth helper, browser automation library, or existing repo tooling is the reason the CLI can be better. Use Python when the source is data science, local file transforms, notebooks, SQLite/CSV/JSON analysis, or Python-heavy admin tooling that can still be installed as a durable command. Do not pick a language that adds setup friction unless it materially improves the CLI. If the best language is not installed, either install the missing toolchain with the user's approval or choose the next-best installed option. State the choice in one sentence before scaffolding, including the reason and the installed toolchain you found. Command Contract Sketch the command surface in chat before coding. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills openai/cli-creator