cli-creator

Builds composable command-line tools from API docs, OpenAPI specs, or curl examples.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/ironkid90-s/lucky5-v7 --skill cli-creator-ironkid90-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-creator
Source: https://github.com/ironkid90-s/lucky5-v7/tree/main/.github/skills/cli-creator
Command: npx skills add https://github.com/ironkid90-s/lucky5-v7 --skill cli-creator-ironkid90-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an API, web app, or ad-hoc script into a durable, installable CLI that an AI agent can run from any repository is repetitive and error-prone; this Skill standardizes the entire process from source analysis to PATH installation. ## Core Features & Use Cases - Source-to-CLI scaffolding: Converts API docs, OpenAPI specs, curl examples, SDKs, or existing scripts into a structured CLI with discovery, resolve, read, write, and raw escape-hatch commands. - Runtime selection guidance: Chooses between Rust, TypeScript/Node, or Python based on installed toolchains and source material, with recommended crates and libraries for each. - Auth, JSON, and safety conventions: Enforces token precedence (env, config file, flag), stable --json output, doctor diagnostics, and draft/dry-run write paths. - Use Case: Given a set of DevTools curl captures from an internal admin app, generate a admin-cli binary installed in ~/.local/bin with doctor, resource listing, and a companion skill teaching future agents how to use it. ## Quick Start Ask the agent to use the cli-creator skill to build a CLI from your API documentation or curl examples, install it on PATH, and create a companion skill for it.

Frequently Asked Questions about cli-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn an API into a command-line tool?

Inventory the API's resources, auth, pagination, and write actions from its docs or OpenAPI spec, then scaffold a CLI with discovery, resolve, read, and narrow write commands. Install the binary on PATH and smoke test it from a directory outside the source folder.

What language should I use to build a CLI tool?

Default to Rust for a single fast binary with clap, reqwest, and serde. Choose TypeScript/Node when an official SDK or browser automation library matters, and Python for data-heavy or script-wrapping workflows, based on what toolchains are already installed.

How should a CLI handle API tokens and authentication?

Support environment variables first using the service's standard name, then a user config file such as ~/.tool-name/config.toml, and token flags only for one-off tests. Never print full tokens, and have a doctor command report the auth source category.

Can I build a CLI from browser DevTools curl captures?

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

What commands should a well-designed CLI expose?

Expose --help, a doctor command for config and auth checks, discovery commands for top-level containers, resolve commands mapping names to IDs, read commands, narrow write commands with dry-run support, and a raw request escape hatch.

When should I write a script instead of a full CLI?

Write a plain script in the current repo when it solves a one-off task. Reserve a durable installed CLI for tools that future sessions will run repeatedly by command name from any working directory.