name: Create a CLI Codex can use tagline: Give Codex a composable command for an API, log source, export, or team script. summary: Ask Codex to create a composable CLI it can run from any folder, combine with repo scripts, use to download files, and remember through a companion skill. skills:
-
token: $cli-creator url: https://github.com/openai/skills/tree/main/skills/.curated/cli-creator description: Design the command surface, build the CLI, add setup and auth checks, install the command on PATH, and verify it from another folder.
-
token: $skill-creator url: https://github.com/openai/skills/tree/main/skills/.system/skill-creator description: Create the companion skill that teaches later Codex tasks which CLI commands to run first and which write actions require approval. bestFor:
-
Repeated work where Codex needs to search, read, download from, or safely write to the same service, export, local archive, or repo script.
-
Agent tools that need paged search, exact reads by ID, predictable JSON, downloaded files, local indexes, or draft-before-write commands. starterPrompt: title: Build a CLI and companion skill body: >- Use $cli-creator to create a CLI you can use, and use $skill-creator to create the companion skill in this same thread.
Source to learn from: [docs URL, OpenAPI spec, redacted curl command, existing script path, log folder, CSV or JSON export, SQLite database path, or pasted --help output].
First job the CLI should support: [download failed CI logs from a build URL, search support tickets and read one by ID, query an admin API, read a local database, or run one step from an existing script].
Optional write job: [create a draft comment, upload media, retry a failed job, or read-only for now].
Command name: [cli-name, or recommend one].
Before coding, show me the proposed command surface and ask only for missing details that would block the build. relatedLinks:
-
label: Codex skills url: /codex/skills
-
label: Create custom skills url: /codex/skills/create-skill
Introduction
When Codex keeps using the same API, log source, exported inbox, local database, or team script, give that work a composable interface: a command it can run from any folder, inspect, narrow, and combine with git, gh, rg, tests, and repo scripts.
Add a companion skill that records when Codex should use the CLI, what to run first, how to keep output small, where downloaded files land, and which write commands need approval.
In this workflow, $cli-creator helps Codex build the command. $skill-creator helps Codex save a reusable skill such as $ci-logs, which future tasks can invoke by name.
How to use
- Decide whether the job needs a CLI
- Share the source Codex should learn from
- Run
$cli-creator - Test the installed command
- Invoke the saved skill later
Choose what the CLI should do
Start with the thing you want Codex to do, not the technology you want it to write. A good CLI turns a repeated read, search, download, export, draft, upload, poll, or safe write into a command Codex can run from any repo.
| Situation | What Codex can do with the CLI |
|---|---|
| CI logs live behind a build page. | Take a build URL, download failed job logs to ./logs, and return file paths plus short snippets. |
| Support tickets arrive as a weekly export. | Index the newest CSV or JSON export, search by customer or phrase, and read one ticket by stable ID. |
| An API response is too large for context. | List only the fields it needs, read the full object by ID, and export the complete response to a file. |
| A Slack export has long threads. | Search with --limit, read one thread, and return nearby context instead of the whole archive. |
| A team script runs four different steps. | Split setup, discovery, download, draft, upload, poll, and live write into separate commands. |
| A plugin finds the record, but Codex needs a file. | Keep the plugin in the thread; use a CLI to download the attachment, trace, report, video, or log bundle and return the path. |
Share the docs, files, or commands
Codex needs something concrete to learn from: docs or OpenAPI, a redacted curl command, an export or database path, a log folder, or an existing script. If you want the CLI to follow a familiar style, paste a short --help output from gh, kubectl, or your team's own tool.
If the command needs auth, tell Codex the environment variable name, config file path, or login flow it should support. Set the secret yourself in your shell or config file. Do not paste secrets into the thread. Ask Codex to make the CLI's setup check fail clearly when auth is missing.
Ask Codex to build the CLI and skill
Use the starter prompt on this page. Fill in the source Codex should learn from and the first job the CLI should support.
Before Codex writes code, it should show the proposed command surface and ask only for missing details that would block the build.
Verify the command works from any folder
Codex should not stop after cargo run, python path/to/script.py, or an uninstalled package command. Ask it to test the installed command from another repo or a temporary folder, the way a later task will use it.
Test the CLI like a future agent
If Codex returns a giant JSON blob, ask it to narrow the default response and add a file export for full payloads. If it forgets the approval boundary, ask it to update the companion skill before you use it in another thread.
Use the skill later
When you need the CLI again, invoke the skill instead of pasting the docs again:
For recurring work, test the skill once in a normal thread, then ask Codex to turn that same invocation into an automation.