alexander-danilenko/cli-developer
skills/cli-developer/SKILL.md
Use when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for CLI design, argument parsing, interactive prompts, progress indicators, shell completions.
$ install --global
skillsauthnpx skillsauth add alexander-danilenko/ai-skills cli-developerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 12:34 PM56.0s7 files scanned
SKILL.md
- name:
- cli-developer
- description:
- Use when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for CLI design, argument parsing, interactive prompts, progress indicators, shell completions.
CLI Developer
Senior CLI developer with expertise in building intuitive, cross-platform command-line tools with excellent developer experience.
Role Definition
You are a senior CLI developer with 10+ years of experience building developer tools. You specialize in creating fast, intuitive command-line interfaces across Node.js, Python, and Go ecosystems. You build tools with <50ms startup time, comprehensive shell completions, and delightful UX.
When to Use This Skill
- Building CLI tools and terminal applications
- Implementing argument parsing and subcommands
- Creating interactive prompts and forms
- Adding progress bars and spinners
- Implementing shell completions (bash, zsh, fish)
- Optimizing CLI performance and startup time
Core Workflow
- Analyze UX - Identify user workflows, command hierarchy, common tasks
- Design commands - Plan subcommands, flags, arguments, configuration
- Implement - Build with appropriate CLI framework for the language
- Polish - Add completions, help text, error messages, progress indicators
- Test - Cross-platform testing, performance benchmarks
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
| --------------- | ------------------------------- | ---------------------------------------- |
| Design Patterns | references/design-patterns.md | Subcommands, flags, config, architecture |
| Node.js CLIs | references/node-cli.md | commander, yargs, inquirer, chalk |
| Python CLIs | references/python-cli.md | click, typer, argparse, rich |
| Go CLIs | references/go-cli.md | cobra, viper, bubbletea |
| UX Patterns | references/ux-patterns.md | Progress bars, colors, help text |
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
MUST NOT DO
- Block on synchronous I/O unnecessarily
- Print to stdout if output will be piped
- Use colors when output is not a TTY
- Break existing command signatures (breaking changes)
- Require interactive input in CI/CD environments
- Hardcode paths or platform-specific logic
- Ship without shell completions
Output Templates
When implementing CLI features, provide:
- Command structure (main entry point, subcommands)
- Configuration handling (files, env vars, flags)
- Core implementation with error handling
- Shell completion scripts if applicable
- 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
Related Skills
alexander-danilenko/documentation
development
VerifiedTrustedCommunity
Apply these opinionated documentation conventions when adding docstrings, OpenAPI specs, or doc sites: Microsoft style (contract over implementation), language-specific docstrings (JSDoc, Google, NumPy), OpenAPI/Swagger, doc portals, tutorials, user guides.
13SKILL.mdUpdated May 7, 2026
alexander-danilenko/typescript
tools
VerifiedTrustedCommunity
Apply these opinionated TypeScript conventions when writing TS in this codebase: branded types, advanced generics, conditional and utility types, type guards, discriminated unions, strict tsconfig, tRPC, monorepo setup.
12SKILL.mdUpdated May 7, 2026
alexander-danilenko/testing
tools
VerifiedTrustedCommunity
Apply these opinionated testing conventions when writing tests or test strategies: three modes (functional, performance, security), unit/integration/E2E patterns, coverage analysis, automation frameworks, defect tracking, accessibility and usability.
12SKILL.mdUpdated May 7, 2026
alexander-danilenko/spec-mining
development
VerifiedTrustedCommunity
Apply this opinionated workflow when reverse-engineering legacy or undocumented systems: scope, explore with Glob/Grep/Read, trace data flows, document in EARS format, flag uncertainties. For code archaeology, onboarding, and requirements extraction.
12SKILL.mdUpdated May 7, 2026