cli-creatorlisted

# 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: ```bash command -v <tool-name> || true ``` 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: ```bash command -v cargo rustc node pnpm npm python3 uv || true ``` 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 t