create-cli

Design CLI parameters, flags, subcommands, help text, and error messages.

5|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/marchatton/agent-skills --skill create-cli-marchatton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-cli
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/00-utilities/create-cli
Command: npx skills add https://github.com/marchatton/agent-skills --skill create-cli-marchatton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design user-friendly and effective command-line interfaces (CLIs) by defining their arguments, flags, subcommands, and overall user experience before implementation.

Core Features & Use Cases

  • CLI Design: Define the syntax, behavior, and UX of CLIs.
  • Parameter Specification: Detail arguments, flags, subcommands, and help text.
  • Use Case: You need to design a new CLI tool for managing cloud resources. This Skill will help you define its structure, available commands (like create, delete, list), and options (like --region, --force) to ensure it's intuitive for developers.

Quick Start

Design a CLI command named 'deploy' that accepts a 'target-environment' argument and a '--force' flag.

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 command-line interface for a new developer tool?

To design command-line interface parameters, you define the tool's arguments, flags, and subcommands, along with help text, output formats, error messages, exit codes, and configuration precedence to ensure discoverability.

What's the best way to structure CLI arguments and flags for developer tools?

Structuring CLI arguments and flags requires specifying their behavior, syntax, and configuration precedence, ensuring that commands like 'create' or 'delete' and options like '--force' are consistent and easy to discover.

Can I use this approach to refactor existing command-line interfaces for consistency?

Yes, you can refactor existing command-line interfaces by re-evaluating their parameters, user experience, and output formats to improve overall consistency, discoverability, and user friendliness.

What components should I include in a CLI specification?

A complete CLI specification should include subcommands, arguments, flags, help text, output formats, error messages, exit codes, prompts, and configuration precedence rules to define the full user experience.

When do I need to define configuration precedence for a command-line tool?

You need to define configuration precedence when your command-line tool accepts inputs from multiple sources like flags, prompts, and configuration files, ensuring predictable behavior and correct parameter resolution.