skills.rest
doubleflannel
doubleflannelCOMMUNITY
Explore all skills by this author →
GitHub

create-cli

Design complete CLI specifications with command trees, flags, and exit codes.

Updated Aug 23, 2026
Search Tags:#design#cli#usability#spec#parser#command-line
One-click install
npx skills add https://github.com/doubleflannel/12-30-test-codex-ip --skill create-cli-doubleflannel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-cli
Source: https://github.com/doubleflannel/12-30-test-codex-ip/tree/main/skills/create-cli
Command: npx skills add https://github.com/doubleflannel/12-30-test-codex-ip --skill create-cli-doubleflannel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designing a CLI surface area is time-consuming and error-prone; this skill provides a structured blueprint to ensure consistency, usability, and scriptability.

Core Features & Use Cases

  • Command tree design with clear USAGE and help text
  • Args/flags, subcommands, output formats, error handling, and config precedence
  • Examples to illustrate common workflows across platforms

Quick Start

Provide a complete CLI surface-area spec for a hypothetical tool named 'mytool' with at least three subcommands.

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 that is easy for humans but still works for scripts?▼

Designing a CLI for both humans and scripts requires a specification covering arguments, flags, subcommands, help text, output formats, error handling, and exit codes. This ensures consistency, usability, and scriptability.

What is the best way to structure command-line tool help text and usage syntax?▼

The best way to structure command-line tool help text is by creating a command tree with a clear USAGE synopsis. A complete specification also defines global flags, I/O contracts, and 5-10 cross-platform example invocations to illustrate workflows.

How do I specify configuration precedence and environment rules for a command-line tool?▼

Specify configuration precedence and environment rules by defining env/config rules within a complete CLI surface-area specification. This blueprint maps typical usage scenarios to ensure consistent behavior across different invocation contexts.

How do I design error handling and exit codes for a CLI parser?▼

Design CLI error handling and exit codes by mapping specific error conditions to standardized exit codes within your specification. A complete spec includes I/O contracts and error handling rules to ensure scriptable and predictable command-line behavior.

Can I generate a language-agnostic specification for a command-line tool with multiple subcommands?▼

Yes, you can generate a language-agnostic specification for a command-line tool. The specification delivers a complete command tree, USAGE synopsis, global flags, I/O contracts, and example invocations that work across platforms.

Related Skills

Explore More Software Engineering Skills→
vlad-ryzhkovvlad-ryzhkov
25

repo-scout

Audit Go backend repositories for API endpoints, infrastructure, and test coverage.

Community
Intermediate
ConsiliencyConsiliency
8

treesitter-patterns

Provide framework-agnostic tree-sitter patterns for AST parsing and query creation.

Official
Intermediate
krzemienskikrzemienski
2

cli-validation

Validate CLI binaries and capture stdout, stderr, and exit codes.

Community
Intermediate
cajiascajias

cc-slash-command-argument-hint-yaml

Quote argument-hint placeholders in Claude Code slash command frontmatter to fix YAML parsing.

Community
Intermediate