What problem does it solve? Human-oriented CLIs often block automation: interactive prompts, arrow-key menus, missing examples in help text, and non-idempotent commands cause coding agents to hang or fail. This Skill provides design guidelines for building CLIs that agents can run headlessly and compose in pipelines. ## Core Features & Use Cases - Non-interactive design patterns: Ensures every input is expressible as a flag, with interactive mode only as a fallback. - Layered help and examples: Structures --help per subcommand with copy-pasteable example invocations instead of dumping full manuals. - Agent-safe behaviors: Covers stdin/pipeline support, fast actionable errors, idempotency, --dry-run, --force flags, and machine-useful success output. - Use Case: When building a new deploy CLI, apply these patterns so an agent can run mycli deploy --env staging --tag v1.2.3 --force without prompts, preview changes with --dry-run, and parse structured output like deploy IDs and URLs. ## Quick Start Ask the agent to review your CLI's command structure and help output against agent-friendly design patterns, or to design a new non-interactive CLI command with flags, examples, and dry-run support.