cli-creator

Provide the API docs, OpenAPI spec, or curl examples as source material, then define the target jobs like listing resources or downloading logs. The Skill scaffolds a CLI with discovery, resolve, read, and write commands, installs it on PATH, and smoke-tests it from outside the source folder.

Rust is the default for durable CLIs because it produces one fast binary with strong argument parsing and JSON handling. Use TypeScript/Node when an official SDK or browser automation library matters, and Python for data-heavy or script-wrapping workflows.

Support environment variables first using the service's standard name, then a user config file, then a token flag only for one-off tests. Never print full tokens, and make the doctor command report the auth source category and any missing setup steps.

Yes, but first create sanitized endpoint notes covering method, path, headers, auth mechanism, request body, and pagination. Never commit copied cookies, bearer tokens, customer secrets, or full production payloads into the CLI repository.

Expose a doctor command for config and auth checks, discovery commands for top-level containers, resolve commands that turn names or URLs into stable IDs, narrow read and write commands with --json, and a raw request escape hatch. Avoid hiding writes inside broad commands like fix or debug.

Do not use it for one-off tasks where a short script in the current repo solves the problem. This Skill targets durable tools that future sessions will run repeatedly by command name from any working directory.