# Design Better CLI Commands

CLI commands often grow inconsistent, unclear, or hard to maintain. This skill helps Claude, Codex, and Claude Code design usable commands, arguments, error handling, and documentation.

## Install

```bash
npx skillstore add joseph obrien/89jobrien-command-optimization
```

## Metadata

- Status: approved
- Slug: 89jobrien-command-optimization
- Version: 1.0.1
- Author version: 1.0.1
- Skillstore revision: r1
- Version status: valid
- Tree hash: bc7699d6d4ddaab9542046909a48141a9ddc12d150e24849e957687bd05cee93
- Author: Joseph OBrien
- GitHub username: 89jobrien
- License: MIT
- Repository: https://github.com/89jobrien/steve/tree/main/steve/skills/command-optimization
- Ref: c4037264bbd363c572662d6154a3ab28f5ca4f53
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/89jobrien-command-optimization
- Manifest: https://skillstore.pages.dev/api/skills/89jobrien-command-optimization/manifest

## Capabilities

- Designs task-oriented CLI command names, options, and usage patterns.
- Reviews command examples for clearer arguments and safer defaults.
- Drafts help text, error messages, and usage documentation.
- Creates slash command templates with frontmatter, arguments, workflows, and output formats.
- Explains validation, dry-run, confirmation, and verbose-mode patterns.

## Use Cases

- Create Developer Commands: Design a new project command with clear usage, options, examples, and validation rules.
- Improve Existing CLI Workflows: Review confusing commands and refine names, flags, feedback, and error messages.
- Standardize Slash Command Templates: Draft reusable slash command structure with frontmatter, arguments, workflow steps, and output format.

## Prompt Templates

### Draft a Basic Command

```
Create a simple CLI command for [task]. Include the command name, purpose, required arguments, optional flags, and one usage example.
```

### Improve a Command Interface

```
Review this command: [command]. Improve the name, arguments, options, help text, validation, and error messages.
```

### Create a Safe Slash Command Template

```
Design a slash command template for [workflow]. Include frontmatter, arguments, workflow steps, output format, and safety notes for any dynamic context.
```

### Design a Command Suite

```
Create a command suite for [project workflow]. Define consistent command names, shared options, validation rules, dry-run behavior, and documentation structure.
```

## Limitations

- It provides guidance and templates, not a tested CLI framework.
- It does not include executable scripts or argument-parsing libraries.
- Dynamic shell context in slash command templates requires careful review before use.
- Generated commands still need project-specific implementation and tests.

## Best Practices

- Start with a clear action verb, target object, and one primary task.
- Add dry-run, confirmation, and validation for commands that change files or data.
- Keep examples, help text, and error messages aligned with real project conventions.

## Anti Patterns

- Using vague command names such as check, run, or make without context.
- Adding force or rollback options without safeguards or clear warnings.
- Copying dynamic shell context into slash commands without reviewing what executes.

## Security Audit

- Audited at: 2026-07-05T11:32:25.654\+00:00
- Summary: Most static findings in SKILL.md are false positives from Markdown fences, inline option names, and documented examples. The reference template contains real slash-command dynamic context using shell commands that execute when copied into a command. No prompt injection, data exfiltration intent, or malicious command content was found.

## Stats

- Views: 238
- Downloads: 14
- Favorites: 0
- Popularity score: 0