Agent skill

CLI Developer

by Jeffallan in Jeffallan/claude-skills

Walks through designing, building and polishing a command-line tool: user workflow and command hierarchy, implementation in commander, click, typer or cobra, completions and cross-platform testing.

MITAuto-check passedDevelopment

Install CLI Developer

skills CLI
$ npx skills add Jeffallan/claude-skills --skill cli-developer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Jeffallan/claude-skills cli-developer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Jeffallan/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cli-developer .claude/skills/cli-developer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cli-developer
GitHub stars
12k
Used in
2 other repos
Token cost
~1.2k tokens
SKILL.md length
381 words
Files
6 (incl. references)
Skills in repo
58
Repo updated
First seen
Licence
MIT

At a glance

Walks through designing, building and polishing a command-line tool: user workflow and command hierarchy, implementation in commander, click, typer or cobra, completions and cross-platform testing.

  • Works in 5 steps: Analyze UX — Identify user workflows,… → Design commands — Plan subcommands,… → Implement — Build with the appropriate… → …
  • Designing a command hierarchy and flags for a new CLI tool
  • SKILL.md covers Core Workflow, Reference Guide, Quick-Start Example and Constraints, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The workflow runs five steps: analyze the user's workflows and command hierarchy, validating by listing every command's expected help output before writing code; design subcommands, flags and configuration with consistent naming that does not break existing signatures; implement with the right framework for the language, checking that --help and --version render correctly after wiring commands up; polish with shell completions, error messages and progress indicators, verifying TTY detection for color and graceful SIGINT handling; and test across platforms while benchmarking startup time against a 50 millisecond target.

Reference files are loaded by topic: design patterns for subcommands and architecture, node-cli.md for commander, yargs, inquirer and chalk, python-cli.md for click, typer, argparse and rich, go-cli.md for cobra, viper and bubbletea, and ux-patterns.md for progress bars, colors and help text, each with a quick-start example. Firm rules include writing diagnostics to stderr rather than stdout when output may be piped, detecting TTY before applying color in any of the three languages, validating input early and supporting both interactive and non-interactive modes.

When your agent uses it

  • Designing a command hierarchy and flags for a new CLI tool
  • Implementing a CLI with commander, click, typer or cobra
  • Adding shell completion scripts, progress bars or proper SIGINT handling
  • Reviewing a CLI for TTY detection and piping behavior

Example prompts

  • “Design the subcommand structure for a CLI that manages database migrations.”
  • “Implement this CLI in Python with typer, including bash completion.”
  • “Review my Node CLI for TTY color detection and SIGINT handling.”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Analyze UX — Identify user workflows, command hierarchy, common tasks. Validate by listing all commands and their expected --help output…
  2. Design commands — Plan subcommands, flags, arguments, configuration. Confirm flag naming is consistent and no existing signatures are…
  3. Implement — Build with the appropriate CLI framework for the language (see Reference Guide below). After wiring up commands, run --help to…
  4. Polish — Add completions, help text, error messages, progress indicators. Verify TTY detection for color output and graceful SIGINT…
  5. Test — Run cross-platform smoke tests; benchmark startup time (target: <50ms).

What it can do on your machine

Read from SKILL.md and the folder at commit 1be15d8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript, python and go).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • synergetic.solutions
    • jeffallan.github.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CLI Developer loads about 1.2k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 381 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Jeffallan/claude-skills at commit 1be15d8, republished under its MIT licence (© Jeffallan). 381 words, ~1,192 tokens.

Download SKILL.mdSave it as .claude/skills/cli-developer/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
cli-developer
description
Use when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for parsing flags and subcommands, displaying progress bars and spinners, generating bash/zsh/fish completion scripts, CLI design, shell completions, and cross-platform terminal applications using commander, click, typer, or cobra.
license
MIT
metadata.author
https://github.com/Jeffallan
metadata.company
https://synergetic.solutions
metadata.version
1.1.0
metadata.domain
devops
metadata.triggers
CLI, command-line, terminal app, argument parsing, shell completion, interactive prompt, progress bar, commander, click, typer, cobra
metadata.role
specialist
metadata.scope
implementation
metadata.output-format
code
metadata.related-skills
devops-engineer

CLI Developer

Core Workflow

  1. Analyze UX — Identify user workflows, command hierarchy, common tasks. Validate by listing all commands and their expected --help output before writing code.
  2. Design commands — Plan subcommands, flags, arguments, configuration. Confirm flag naming is consistent and no existing signatures are broken.
  3. Implement — Build with the appropriate CLI framework for the language (see Reference Guide below). After wiring up commands, run <cli> --help to verify help text renders correctly and <cli> --version to confirm version output.
  4. Polish — Add completions, help text, error messages, progress indicators. Verify TTY detection for color output and graceful SIGINT handling.
  5. Test — Run cross-platform smoke tests; benchmark startup time (target: <50ms).

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Design Patternsreferences/design-patterns.mdSubcommands, flags, config, architecture
Node.js CLIsreferences/node-cli.mdcommander, yargs, inquirer, chalk
Python CLIsreferences/python-cli.mdclick, typer, argparse, rich
Go CLIsreferences/go-cli.mdcobra, viper, bubbletea
UX Patternsreferences/ux-patterns.mdProgress bars, colors, help text

Quick-Start Example

Node.js (commander)
js
#!/usr/bin/env node
// npm install commander
const { program } = require('commander');

program
  .name('mytool')
  .description('Example CLI')
  .version('1.0.0');

program
  .command('greet <name>')
  .description('Greet a user')
  .option('-l, --loud', 'uppercase the greeting')
  .action((name, opts) => {
    const msg = `Hello, ${name}!`;
    console.log(opts.loud ? msg.toUpperCase() : msg);
  });

program.parse();

For Python (click/typer) and Go (cobra) quick-start examples, see references/python-cli.md and references/go-cli.md.

Constraints

MUST DO
  • Keep startup time under 50ms
  • Provide clear, actionable error messages
  • Support --help and --version flags
  • Use consistent flag naming conventions
  • Handle SIGINT (Ctrl+C) gracefully
  • Validate user input early
  • Support both interactive and non-interactive modes
  • Test on Windows, macOS, and Linux
Show full SKILL.md (180 more words)Show less
MUST NOT DO
  • Block on synchronous I/O unnecessarily — use async reads or stream processing instead.
  • Print to stdout when output will be piped — write logs/diagnostics to stderr.
  • Use colors when output is not a TTY — detect before applying color:
    js
    // Node.js
    const useColor = process.stdout.isTTY;
    python
    # Python
    import sys
    use_color = sys.stdout.isatty()
    go
    // Go
    import "golang.org/x/term"
    useColor := term.IsTerminal(int(os.Stdout.Fd()))
  • Break existing command signatures — treat flag/subcommand renames as breaking changes.
  • Require interactive input in CI/CD environments — always provide non-interactive fallbacks via flags or env vars.
  • Hardcode paths or platform-specific logic — use os.homedir() / os.UserHomeDir() / Path.home() instead.
  • Ship without shell completions — all three frameworks above have built-in completion generation.

Output Templates

When implementing CLI features, provide:

  1. Command structure (main entry point, subcommands)
  2. Configuration handling (files, env vars, flags)
  3. Core implementation with error handling
  4. Shell completion scripts if applicable
  5. Brief explanation of UX decisions

Knowledge Reference

CLI frameworks (commander, yargs, oclif, click, typer, argparse, cobra, viper), terminal UI (chalk, inquirer, rich, bubbletea), testing (snapshot testing, E2E), distribution (npm, pip, homebrew, releases), performance optimization

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

© Jeffallan, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/cli-developer of Jeffallan/claude-skills.

  • SKILL.md
  • references/design-patterns.md
  • references/go-cli.md
  • references/node-cli.md
  • references/python-cli.md
  • references/ux-patterns.md

Open the folder on GitHubat commit 1be15d8

Used in 2 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in Jeffallan/claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

CLI Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

CLI Developer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
CLI Developer this skillJeffallan/claude-skills12k2 repos~1.2kAutomated safety check: PassMIT
Claude Code Statusline Writerlexler/skill-factory239—~872Automated safety check: PassApache-2.0
Hns Moaiadk Dev Referencemodu-ai/moai-adk1.2k—~937Automated safety check: PassApache-2.0
Hugging Face API Tool Builderhuggingface/skills11k5 repos~1.5kAutomated safety check: PassApache-2.0
New Mac Setupswyxio/skills175—~4.3kAutomated safety check: PassMIT
Mole Bug Patternstw93/Mole70k—~2kAutomated safety check: PassGPL-3.0

Similar skills

  • Claude Code Statusline Writer

    lexler/skill-factory

    Guides writing and debugging Claude Code status line scripts that read session JSON from stdin and print one line of text.

    239 GitHub stars~872 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • moai-adk-go local dev reference — version management/release process (sec 5), shell-script hook development (sec 7), build & dev commands (sec 10).

    1.2k GitHub stars~937 tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    Builds reusable command line scripts that fetch, enrich or process data from the Hugging Face API, aimed at chained, repeated or automated tasks.

    11k GitHub starsUsed in 5 repos~1.5k tokens
    AI & LLM EngineeringAuto-check passed
  • New Mac Setup

    swyxio/skills

    Fully automated new Mac setup for fullstack web developers and AI engineers.

    175 GitHub stars~4.3k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • JSON Processing with jq

    charmbracelet/crush

    Explains the jq command built into Crush for querying, filtering and reshaping JSON, including its supported flags and where it differs from standard jq.

    29k GitHub stars~746 tokensUpdated today
    DevelopmentAuto-check passed

More from Jeffallan/claude-skills

All 58 skills in this repo
  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 2 repos~2k tokens
    Auto-check passed
  • Fine-Tuning Expert

    Jeffallan/claude-skills

    Guides LLM fine-tuning with LoRA and QLoRA through Hugging Face PEFT, from dataset validation and training checks to adapter merging, quantization and deployment.

    12k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • GraphQL Architect

    Jeffallan/claude-skills

    Designs GraphQL schemas and Apollo Federation graphs, with DataLoader resolvers, subscriptions, query complexity limits and caching.

    12k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Kubernetes Specialist

    Jeffallan/claude-skills

    Creates and checks Kubernetes manifests, Helm charts, RBAC and network policies, and helps debug pod problems, with kubectl checks and rollback steps.

    12k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Laravel Specialist

    Jeffallan/claude-skills

    Builds Laravel 10+ applications with Eloquent models, Sanctum authentication, Horizon queues, API resources and Livewire components, tested with Pest or PHPUnit.

    12k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • ML Pipeline Expert

    Jeffallan/claude-skills

    Designs ML pipeline infrastructure: experiment tracking with MLflow or Weights & Biases, Kubeflow and Airflow orchestration, Feast feature stores and model validation gates.

    12k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

Works with

Categories

Questions about CLI Developer

What does CLI Developer do?

Walks through designing, building and polishing a command-line tool: user workflow and command hierarchy, implementation in commander, click, typer or cobra, completions and cross-platform testing. The workflow runs five steps: analyze the user's workflows and command hierarchy, validating by listing every command's expected help output before writing code; design subcommands, flags and configuration with consistent naming that does not break existing signatures; implement with the right framework for the language, checking that --help and --version render correctly after wiring commands up; polish with shell completions, error messages and progress indicators, verifying TTY detection for color and graceful SIGINT handling; and test across platforms while benchmarking startup time against a 50 millisecond target.

When should I use CLI Developer?

CLI Developer fits situations like: designing a command hierarchy and flags for a new CLI tool; implementing a CLI with commander, click, typer or cobra; adding shell completion scripts, progress bars or proper SIGINT handling; reviewing a CLI for TTY detection and piping behavior.

How do I install CLI Developer in Claude Code?

Run `npx skills add Jeffallan/claude-skills --skill cli-developer -a claude-code`. Or copy the skill folder (skills/cli-developer in Jeffallan/claude-skills) into .claude/skills/cli-developer in your project. Claude Code loads it when a task matches its description.

How do I install CLI Developer in Codex?

Run `npx skills add Jeffallan/claude-skills --skill cli-developer -a codex`. Or copy the skill folder (skills/cli-developer in Jeffallan/claude-skills) into .agents/skills/cli-developer in your project. Codex loads it when a task matches its description.

Can I use CLI Developer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jeffallan/claude-skills --skill cli-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cli-developer, .gemini/skills/cli-developer, .github/skills/cli-developer and .opencode/skills/cli-developer in your project.

What does CLI Developer need to run?

SKILL.md names no scripts, command-line tools or credentials: CLI Developer is instructions for the agent only.

Does CLI Developer access the network?

SKILL.md names 3 domains. As links in the text: github.com, synergetic.solutions and jeffallan.github.io. This is read from the text; nothing was executed.

Is CLI Developer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does CLI Developer use?

CLI Developer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CLI Developer use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to CLI Developer?

Skills that share tags, products or a category with CLI Developer: Claude Code Statusline Writer (lexler/skill-factory, 239 stars), Hns Moaiadk Dev Reference (modu-ai/moai-adk, 1.2k stars), Hugging Face API Tool Builder (huggingface/skills, 11k stars) and New Mac Setup (swyxio/skills, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CLI Developer?

Jeffallan (a GitHub user) maintains it in Jeffallan/claude-skills, which has 11,767 GitHub stars. The repository holds 58 skills in this directory. The repository was last updated on October 3, 2026.

Source: Jeffallan/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.