Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.

I understand these skills can contain unsafe or unintended behavior, and I will review and security-scan before use. No warranty, suitability, or outcome is guaranteed.

Developer ExperienceFree Safe

Cli Developer

Security Scan Summary

Status: Safe

Source: Syntic Skills registry

Automated security scan completed with no high-risk patterns detected. Manual review is still required.

About This Skill

Use when building robust CLI tools using Commander.js, yargs, clap with polished interfaces and shell completion.

Downloadable SKILL.md

Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.

SKILL.md

---
name: Cli Developer
description: Use when building robust CLI tools using Commander.js, yargs, clap with polished interfaces and shell completion.
category: Developer Experience
version: 1.0.0
tools: []
---

# CLI Development

Designs and builds command-line interfaces that feel intuitive and professional.

## Key Steps

1. Gather requirements: target audience, runtime environment, expected command surface, whether interactive prompts or scripted automation is primary.
2. Select framework: based on language ecosystem (Node.js: Commander.js, yargs, oclif, Ink; Rust: clap, dialoguer; Python: Click, Typer, argparse; Go: cobra, urfave/cli), plugin extensibility needs, subcommand nesting requirements.
3. Design command hierarchy: consistent naming conventions, GNU-style long options with short aliases for common operations.
4. Implement argument parsing: strict validation, custom type coercion, mutually exclusive option groups where semantically required.
5. Build help text: include usage examples not just flag descriptions; ensure `--help` output fits within 80-column terminals.
6. Add output formatting: support for `--json`, `--quiet`, and `--no-color` flags as standard across all commands.
7. Implement configuration precedence: CLI flags override environment variables override config file override defaults.
8. Add shell completion: bash, zsh, fish, and PowerShell where framework supports generation.
9. Write integration tests: invoke the binary as subprocess and assert on stdout, stderr, and exit codes.
10. Package correctly: proper shebang lines, bin field in package.json or Cargo.toml binary targets, verify global install works cleanly.

## Standards

- Exit codes: 0 for success, 1 for general errors, 2 for usage errors (POSIX conventions).
- Output: stderr for diagnostics and progress, stdout for machine-parseable output only.
- Environment: respect NO_COLOR environment variable per https://no-color.org specification.
- Versioning: semantic versioning, display with `--version` flag.
- Signals: handle SIGINT and SIGTERM gracefully with cleanup routines.
- Piping: support stdin piping for commands accepting file input.
- Interactivity: never prompt when stdin is not a TTY.
- Progress: long-running operations display progress indicators with estimated time remaining.

Bundle Download

Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.

Install Targets

Syntic App

1. Create a dedicated folder for this skill in your local skills library.
2. Place SKILL.md into that folder.
3. Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

1. Save SKILL.md in your local Syntic Code skills directory.
2. Keep related files in the same skill folder.
3. Run in a safe environment and validate outputs.

Source

https://github.com/rohitg00/awesome-claude-code-toolkit/blob/main/agents/developer-experience/cli-developer.md

Open Source Link

Developer Experience

Related Skills