Does it support different output formats?

Yes, it provides implementation patterns for --json, --plain, and --quiet modes to ensure scripting friendliness.

Is this skill specific to a certain programming language?

No. While the audit script uses Python, the guidelines and implementation patterns apply to CLI tools written in any language.

What standards does this skill follow?

It follows industry-leading guidelines from clig.dev, POSIX, GNU, and Heroku's 12-factor app principles.

How does it handle interactivity?

It enforces TTY detection and requires --no-input flags to ensure your tools work reliably in non-interactive environments like CI/CD.

Can this skill test my CLI tool automatically?

Yes, it includes a specialized cli_audit.py script to validate exit codes, stream separation, and discoverability.

CLI Development Guidelines

Name: CLI Development Guidelines
Author: outfitter-dev

byoutfitter-dev

•

Developer Tools

Standardizes the design and implementation of command-line interfaces using industry best practices and automated compliance audits.

About

This skill empowers developers to build high-quality, professional CLI tools by providing a structured framework for designing commands, flags, and help output. It ensures 'good citizenship' by enforcing rigorous standards for exit codes, stdout/stderr separation, TTY detection, and scripting compatibility. By utilizing integrated audit scripts and standardized templates, it helps Claude create robust CLI contracts that are safe, discoverable, and compliant with POSIX, GNU, and 12-factor principles.

Key Features

Automated CLI compliance auditing using integrated Python scripts
Script-friendly output modes including JSON support and NO_COLOR compliance
Standardized CLI contracts for commands, flags, and IO behavior
16 GitHub stars
Guidelines for 'good citizenship' including exit codes and stream handling
Templates for help text, error messages, and command specifications

Use Cases

Reviewing an existing CLI for compliance with POSIX and GNU standards
Designing a new command-line tool with a complex sub-command structure
Implementing automated sanity checks to ensure CLI tools work correctly in CI/CD

About

Key Features

Automated CLI compliance auditing using integrated Python scripts
Script-friendly output modes including JSON support and NO_COLOR compliance
Standardized CLI contracts for commands, flags, and IO behavior
16 GitHub stars
Guidelines for 'good citizenship' including exit codes and stream handling
Templates for help text, error messages, and command specifications

Use Cases

Reviewing an existing CLI for compliance with POSIX and GNU standards
Designing a new command-line tool with a complex sub-command structure
Implementing automated sanity checks to ensure CLI tools work correctly in CI/CD