编程

cli-creator

试用

把 API 文档、OpenAPI 规范或现成脚本做成装到 PATH 上的 CLI,让 Codex 在任何仓库里按命令名直接调用。

它能做什么

这个技能带 Codex 从一个来源(API 文档、OpenAPI JSON、curl 示例、SDK、浏览器后台、已有脚本或 shell 历史)出发,先盘点资源、鉴权、分页、ID 和危险写操作,在对话里列出命令清单,再搭出带 doctor、发现、解析、读取、窄范围写命令以及 raw 兜底命令的 CLI,并统一提供稳定的 --json 输出。完成后二进制会装到 PATH,在源码目录之外做冒烟测试,并配一份 companion skill 说明后续线程该按什么顺序调用。

什么时候用它

  • 把内部后台的 DevTools curl 整理成可复用的命令行工具
  • 把一次性脚本或 shell 历史拆成带稳定 ID 和 JSON 输出的工具
  • 基于 OpenAPI 规范或公开 API 文档做一个以读为主的 CLI
  • 给已有服务补一份 companion skill,让后续 Codex 线程知道安全调用顺序

技能文档

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/ when the user wants a personal tool and has not named a repo.

Before scaffolding, check whether the proposed command already exists:

command -v  || 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:

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 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. Include the binary name, discovery commands, resolve or ID-lookup commands, read commands, write commands, raw escape hatch, auth/config choice, and PATH/install command.

When designing the command surface, read references/agent-cli-patterns.md for the expected composable CLI shape.

Build toward this surface:

  • tool-name --help shows every major capability.
  • tool-name --json doctor verifies config, auth, version, endpoint reachability, and missing setup.
  • tool-name init ... stores local config when env-only auth is painful.
  • Discovery commands find accounts, projects, workspaces, teams, queues, channels, repos, dashboards, or other top-level containers.
  • Resolve commands turn names, URLs, slugs, permalinks, customer input, or build links into stable IDs so future commands do not repeat broad searches.
  • Read commands fetch exact objects and list/search collections. Paginated lists support a bounded --limit, cursor, offset, or clearly documented default.
  • Write commands do one named action each: create, update, delete, upload, schedule, retry, comment, draft. They accept the narrowest stable resource ID, support --dry-run, draft, or preview first when the service allows it, and do not hide writes inside broad commands such as fix, debug, or auto.
  • --json returns stable machine-readable output.
  • A raw escape hatch exists: request, tool-call, api, or the nearest honest name.

Do not expose only a generic request command. Give Codex high-level verbs for the repeated jobs.

Document the JSON policy in the CLI README or equivalent: API pass-through versus CLI envelope, success shape, error shape, and one example for each command family. Under --json, errors must be machine-readable and must not contain credentials.

Auth and Config

Support the boring paths first, in this precedence order:

  1. Environment variable using the service's standard name, such as GITHUB_TOKEN.
  2. User config under ~/./config.toml or another simple documented path.
  3. --api-key or a tool-specific token flag only for explicit one-off tests. Prefer env/config for normal use because flags can leak into shell history or process listings.

Never print full tokens. doctor --json should say whether a token is available, the auth source category (flag, env, config, provider default, or missing), and what setup step is missing.

If the CLI can run without network or auth, make that explicit in doctor --json: report fixture/offline mode, whether fixture data was found, and whether auth is not required for that mode.

For internal web apps sourced from DevTools curls, create sanitized endpoint notes before implementing: resource name, method/path, required headers, auth mechanism, CSRF behavior, request body, response ID fields, pagination, errors, and one redacted sample response. Never commit copied cookies, bearer tokens, customer secrets, or full production payloads.

Use screenshots to infer workflow, UI vocabulary, fields, and confirmation points. Do not treat screenshots as API evidence unless they are paired with a network request, export, docs page, or fixture.

Build Workflow

  1. Read the source just enough to inventory resources, auth, pagination, IDs, media/file flows, rate limits, and dangerous write actions. If the docs expose OpenAPI, download or inspect it before naming commands.
  2. Sketch the command list in chat. Keep names short and shell-friendly.
  3. Scaffold the CLI with a README or equivalent repo-facing instructions.
  4. Implement doctor, discovery, resolve, read commands, one narrow draft or dry-run write path if requested, and the raw escape hatch.
  5. Install the CLI on PATH so tool-name ... works outside the source folder.
  6. Smoke test from another repo or /tmp, not only with cargo run or package-manager wrappers. Run command -v , --help, and --json doctor.
  7. Run format, typecheck/build, unit tests for request builders, pagination/request-body builders, no-auth doctor, help output, and at least one fixture, dry-run, or live read-only API call.

If a live write is needed for confidence, ask first and make it reversible or draft-only.

When the source is an existing script or shell history, split the working invocation into real phases: setup, discovery, download/export, transform/index, draft, upload, poll, live write. Preserve the flags, paths, and environment variables the user already relies on, then wrap the repeatable phases with stable IDs, bounded JSON, and file outputs.

For raw escape hatches, support read-only calls first. Do not run raw non-GET/HEAD requests against a live service unless the user asked for that specific write.

For media, artifact, or presigned upload flows, test each phase separately: create upload, transfer bytes, poll/read processing status, then attach or reference the resulting ID.

For fixture-backed prototypes, keep fixtures in a predictable project path and make the CLI locate them after installation. Smoke-test from /tmp to catch binaries that only work inside the source folder.

For log-oriented CLIs, keep deterministic snippet extraction separate from model interpretation. Prefer a command that emits filenames, line numbers or byte ranges, matched rules, and short excerpts.

Rust Defaults

When building in Rust, use established crates instead of custom parsers:

  • clap for commands and help
  • reqwest for HTTP
  • serde / serde_json for payloads
  • toml for small config files
  • anyhow for CLI-shaped error context

Add a Makefile target such as make install-local that builds release and installs the binary into ~/.local/bin.

TypeScript/Node Defaults

When building in TypeScript/Node, keep the CLI installable as a normal command:

  • commander or cac for commands and help
  • native fetch, the official SDK, or the user's existing HTTP helper for API calls
  • zod only where external payload validation prevents real breakage
  • package.json bin entry for the installed command
  • tsup, tsx, or tsc using the repo's existing convention

Add an install path such as pnpm install, pnpm build, and pnpm link --global, or a Makefile target that installs a small wrapper into ~/.local/bin.

Python Defaults

When building in Python, prefer boring standard-library pieces unless the workflow needs more:

  • argparse for commands and help, or typer when subcommands would otherwise get messy
  • urllib.request / urllib.parse, requests, or httpx for HTTP, matching what is already installed or already used nearby
  • json, csv, sqlite3, pathlib, and subprocess for local files, exports, databases, and existing scripts
  • pyproject.toml console script or a small executable wrapper for the installed command
  • uv or a virtualenv only when dependencies are actually needed

Add a Makefile target such as make install-local that installs the command on PATH and document whether it depends on uv, a virtualenv, or only system Python.

Companion Skill

After the CLI works, create or update a small skill for it. Use $skill-creator when it is available. Use $CODEX_HOME/skills//SKILL.md for a personal companion skill unless the user names a repo-local .codex/skills/... path or another skill repo.

Write the companion skill in the order a future Codex thread should use the CLI, not as a tour of every feature. Explain:

  • How to verify the installed command exists.
  • Which command to run first.
  • How auth is configured.
  • Which discovery command finds the common ID.
  • The safe read path.
  • The intended draft/write path.
  • The raw escape hatch.
  • What not to do without explicit user approval.
  • Three copy-pasteable command examples.

Keep API reference details in the CLI docs or a skill reference file. Keep the skill focused on ordering, safety, and examples future Codex threads should actually run.

常见问题

什么时候该用它,而不是直接在仓库里写个脚本?
它面向的是长期可用的工具:后续 Codex 线程能在任意工作目录按命令名调用。如果当前仓库里一个短脚本就能解决问题,文档建议直接写脚本。
CLI 会用哪种语言写?
它会先检查机器上装了哪些工具链,默认用 Rust 做长期可用的 CLI;如果官方 SDK、鉴权辅助库或仓库现有工具链更合适,就用 TypeScript/Node;涉及数据处理、文件转换或 Python 后台工具时用 Python。动手前会用一句话说明选择和理由。
鉴权和密钥怎么处理?
优先读环境变量,其次是文档里写明的用户配置文件,token 命令行参数只用于临时测试。不会打印完整 token,doctor --json 会说明是否拿到 token 以及来源类别。复制来的 cookie、bearer token 和生产数据不会被提交。

相关技能

诊断生产力系统反复失效的根因,给出最小干预——容量测算、瓶颈定位、可靠的本地记录。

作者 Iván857 次安装69 星标

figma-use

官方

通过 Plugin API 在 Figma 文件里执行 JavaScript,并避开那些会让脚本报错的坑。

作者 OpenAI28.8k 星标

按当前官方做法构建、审查和升级 ASP.NET Core 应用,按任务只加载需要的参考文档。

作者 OpenAI28.8k 星标

把一句生成艺术需求变成一份算法哲学文稿,外加可运行的 p5.js 草图,带种子和参数调节。

作者 Anthropic197.6k 星标

从零起草 agent skill,用真实提示词跑测试,再依据定性和定量评估反复迭代。

作者 Anthropic197.6k 星标

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

作者 OpenAI28.8k 星标

OpenAI 的更多技能

浏览全部技能

为 MCP 服务器加 widget 界面的 ChatGPT Apps SDK 应用提供脚手架、重构与排错。

作者 OpenAI28.8k 星标

把代码或描述中的页面转成 Figma 屏幕,并复用已发布的设计系统组件、变量与样式。

作者 OpenAI28.8k 星标

把代码库里的 token 和组件按阶段搬进 Figma,每个阶段都停下来等你确认。

作者 OpenAI28.8k 星标

figma-use

官方

通过 Plugin API 在 Figma 文件里执行 JavaScript,并避开那些会让脚本报错的坑。

作者 OpenAI28.8k 星标

hatch-pet

官方

把概念、品牌线索或参考图做成通过校验的 8x9 Codex 宠物图集,附带 QA 图和 pet.json 打包。

作者 OpenAI28.8k 星标

imagegen

官方

在 Codex 中生成或编辑位图图像,并把需求整理成可直接生产的提示词规格。

作者 OpenAI28.8k 星标