cli-creator

Build composable command-line tools from API docs and OpenAPI specs.

Updated May 26, 2026
One-click install
npx skills add https://github.com/XWIlluDelu/agent-share --skill cli-creator-xwilludelu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-creator
Source: https://github.com/XWIlluDelu/agent-share/tree/main/lib/cli-creator
Command: npx skills add https://github.com/XWIlluDelu/agent-share --skill cli-creator-xwilludelu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you convert messy source material (API docs, OpenAPI specs, curl examples, SDK/web/admin tools, or prior scripts) into a durable command-line interface that agents can run reliably from any repository.

Core Features & Use Cases

  • Composable CLI structure: designs a repeatable command surface for durable agent sessions, including discovery, resolve, read, and safe write/draft flows.
  • Stable JSON contract: enforces machine-readable output and well-defined success/error shapes, with redaction rules for secrets.
  • Auth & config that just works: supports environment-first tokens, config fallbacks, and a diagnostic doctor flow that reports auth sources and missing setup.
  • PATH-installable workflow: guides scaffolding, installation, and smoke testing from outside the source folder to prevent “works only in the repo” failures.

Quick Start

Use the cli-creator skill to generate and install a durable CLI named ci-logs from your log source material, then validate it with cli-logs --json doctor.

Frequently Asked Questions about cli-creator

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

FAQPage Schema
How do I convert OpenAPI specs into a CLI for agent workflows?

The approach scaffolds a PATH-installable CLI from OpenAPI specs or curl examples, enforcing a consistent --json output envelope with redacted errors. This ensures reliable cross-repo execution and prevents works-only-in-the-repo failures.

How do I build a command-line tool from API docs that outputs stable JSON?

Build a command-line tool from API docs by enforcing a well-defined command contract with a consistent --json envelope. This stable JSON output includes machine-readable success and error shapes, applying redaction rules to protect secrets.

Does this CLI scaffolding approach support environment-first auth and config fallbacks?

Yes, the CLI scaffolding supports environment-first tokens, config fallbacks, and a diagnostic doctor flow. The doctor diagnostics report auth sources and missing setup to ensure auth and config just works for durable agent sessions.

What is the best way to generate an agent-ready CLI from existing scripts and SDKs?

The best way to generate an agent-ready CLI from existing scripts and SDKs is to design a repeatable command surface for durable workflows. This includes PATH-installable scaffolding plus smoke tests run from outside the source folder to validate cross-repo execution.

Why do my command-line tools fail when agents run them from outside the source folder?

Command-line tools fail outside the source folder due to improper installation and missing PATH configuration. Scaffolding the CLI with proper installation and running smoke tests from outside the source folder prevents these cross-repo execution failures.