create-cli

Design CLI command trees, arguments, flags, help text, and output formats.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/carlooss-pm/agents --skill create-cli-carlooss-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-cli
Source: https://github.com/carlooss-pm/agents/tree/main/skills/create-cli
Command: npx skills add https://github.com/carlooss-pm/agents --skill create-cli-carlooss-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing CLIs with well-structured commands, predictable UX, and clear help and error messaging, so tools are easy to use and hard to misuse.

Core Features & Use Cases

  • Command tree specification with subcommands and flags.
  • Argument/option semantics, help text, and output formats (stdout/stderr).
  • Config/env precedence, prompts handling, and safe/dry-run behavior.
  • Use Cases: scaffolding CLIs for libraries, automation CLIs for DevOps, and tooling dashboards.

Quick Start

Draft a compact CLI spec for a tool named ExampleTool, including a command tree, arguments, and behavior.

Frequently Asked Questions about create-cli

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

FAQPage Schema
How do I design a CLI interface with predictable command structures and arguments?

To design a CLI interface, you specify a command tree with subcommands, define argument tables and flags, and establish output rules for stdout and stderr. This ensures deterministic command structures and predictable UX across environments.

What is the best way to structure CLI help text and error mapping?

The best way to structure CLI help text and error mapping is to generate a compact spec that includes usage syntax, argument tables, and explicit error mapping. Clear help text makes command-line tools easy to use and hard to misuse.

How does config and environment variable precedence work in command-line tools?

Config and environment variable precedence in command-line tools determines which values override others when setting configurable behavior. Establishing a strict precedence order ensures deterministic execution across different deployment environments.

Can I include dry-run and prompt handling for safe CLI execution?

Yes, you can include dry-run and prompt handling to ensure safe CLI execution. Specifying safety checks and dry-run behavior allows users to preview command actions and configurable behavior without committing potentially destructive changes.

Does this approach work for scaffolding CLIs for DevOps automation?

Yes, this approach works for scaffolding CLIs for DevOps automation and tooling dashboards. By specifying subcommands, flags, and output formats, you create robust command-line interfaces suited for automated environments.

Why do my CLI arguments and flags cause unpredictable UX across environments?

CLI arguments and flags cause unpredictable UX when config and environment precedence is undefined. Resolving this requires a compact spec detailing argument semantics, usage syntax, and strict precedence rules for deterministic behavior.