Back to catalog
Human reviewedDevelopment

Skill dossier

cli-developer

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Guides building command-line tools: plan the command hierarchy, implement with commander, click, typer or cobra, polish UX, and smoke-test across platforms.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Lists commands and expected --help output before writing code.
  • Implements commands with a framework suited to the language and checks --help and --version.
  • Adds shell completions, progress indicators and clear error messages.
  • Checks TTY detection for color, SIGINT handling and non-interactive fallbacks for CI.

Limitations & scope

  • The sub-50ms startup target is a stated goal that is not verified here and may be hard for some runtimes.
  • Cross-platform testing on Windows, macOS and Linux needs access to those environments.
  • Only the Node.js commander example is inline; Python and Go examples are in separate references.

Relevant for

  • Developers building command-line tools
  • Teams standardizing flag naming and help text
  • Maintainers adding shell completions

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
48.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/cli-developer/references/design-patterns.mdReference5.1 KB
skills/cli-developer/references/go-cli.mdReference10.7 KB
skills/cli-developer/references/node-cli.mdReference8.2 KB
skills/cli-developer/references/python-cli.mdReference10.2 KB
skills/cli-developer/references/ux-patterns.mdReference9.9 KB
skills/cli-developer/SKILL.mdInstruction4.7 KB

SKILL.md frontmatter

{
  "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",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "devops",
    "triggers": "CLI, command-line, terminal app, argument parsing, shell completion, interactive prompt, progress bar, commander, click, typer, cobra",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "devops-engineer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze UX

    Identify workflows and command hierarchy, then list all commands with expected --help output.

  2. 02
    Action

    Implement and check help

    Build with the framework for the language, then run the CLI with --help and --version.

  3. 03
    Decision

    Respect the terminal

    Do not use colors when output is not a TTY; detect it before applying color.

  4. 04
    Output

    Deliver CLI package

    Provide the command structure, configuration handling, core code, completions and UX notes.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

80 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

65 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 65 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

9 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 9 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

4 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review any generated install or distribution steps and make sure the CLI never prints secrets or hardcodes platform-specific paths.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/cli-developer # .claude/skills/cli-developer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/cli-developer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm cli-developer/SKILL.md exists at the destination, then ask Claude Code to use the cli-developer skill on a small test task.

Prerequisites

  • The sub-50ms startup target is a stated goal that is not verified here and may be hard for some runtimes.
  • Cross-platform testing on Windows, macOS and Linux needs access to those environments.
  • Only the Node.js commander example is inline; Python and Go examples are in separate references.

Example prompts

Representative task

Use the cli-developer skill to design and implement a Node.js commander CLI called mytool with a greet subcommand, --help and --version, shell completions and a non-interactive mode.

Inspect before use

Read the cli-developer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/cli-developer/SKILL.md and its referenced files. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Concrete MUST NOT rules such as no color when output is not a TTY and no required prompts in CI.
  • Treats flag or subcommand renames as breaking changes.

Considerations

  • Mandates shell completions and tri-platform testing, which can be overkill for small scripts.
  • Framework choice is left to references rather than decided in the main file.
Research conclusion

A solid UX checklist for CLI work, best for tools that will be distributed to other users.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/cli-developer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.