Agent skill
platform-cli
Design and implementation patterns for building command-line tools with modern UX conventions. Use when: (1) designing a new CLI tool, (2) reviewing CLI UX and behavior, (3) defining commands, flags, or help text, (4) implementing error handling or signal handling, (5) planning CLI distribution.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/platform-cli
SKILL.md
CLI Development Patterns
Modern CLI design patterns for commands, flags, output, errors, signals, config, and distribution.
References
See references/cli-patterns.md for comprehensive guidance organized by:
- Design & Naming - Command structure, naming conventions, future-proofing
- Flags & Arguments - Standard flags, short forms, boolean negation
- Output & Formatting - stdout/stderr, TTY detection, colors, machine-readable formats
- Error Handling - Exit codes, error messages, signal-to-noise ratio
- Signals & Lifecycle - Ctrl-C handling, cleanup timeouts
- Environment & Config - Standard variables, precedence, naming
- Distribution & Packaging - Single binary distribution, uninstall instructions
- Security & Privacy - Secret handling, telemetry consent
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?