skills.rest
danielbodnar
danielbodnarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cli-guidelines

Standardize CLI design guidance for Nushell commands, scripts, and plugins.

3|Updated Jan 27, 2026
Search Tags:#help#error-handling#flags#nushell#cli-guidelines#machine-output
One-click install
npx skills add https://github.com/danielbodnar/nushell-dev --skill cli-guidelines-danielbodnar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-guidelines
Source: https://github.com/danielbodnar/nushell-dev/tree/main/plugins/nushell-dev/skills/cli-guidelines
Command: npx skills add https://github.com/danielbodnar/nushell-dev --skill cli-guidelines-danielbodnar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing, implementing, and maintaining effective Nushell CLIs is difficult without a cohesive, documented playbook that ensures clear help, consistent flags, robust error handling, safe prompts, and machine-readable output across tools.

Core Features & Use Cases

  • Centralized CLI design philosophy aligned with clig.dev, tailored for Nushell's structured data model.
  • Practical guidelines for help text, argument/flag patterns, output formats, error reporting, configuration, interactivity, and validation.
  • Real-world applicability across plugins, commands, and scripts to improve discoverability, usability, and automation.

Quick Start

Create a Nushell CLI tool that follows the CLI guidelines for clear help, consistent flags, safe prompts, and machine-readable output.

Frequently Asked Questions about cli-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for designing a Nushell CLI?▼

Nushell CLI design best practices include standardized help text, consistent flag conventions, machine-readable output, robust error handling, and clear interactive patterns aligned with clig.dev.

How do I standardize error handling and flags in Nushell scripts?▼

Standardize error handling and flags in Nushell scripts by applying consistent argument patterns, safe interactive prompts, and validation rules mapped to clig.dev-inspired CLI guidelines.

How do I generate machine-readable output for Nushell commands?▼

Generate machine-readable output for Nushell commands by following CLI guidelines that enforce structured data formats, clear output conventions, and robust error reporting for automation.

Does this CLI guidance apply to both Nushell plugins and custom commands?▼

Yes, these CLI guidelines apply to any Nushell command, script, or plugin requiring consistent help text, flag conventions, and machine-readable output across tools.

What's the best way to structure help text for Nushell tools?▼

Structure help text for Nushell tools using centralized CLI guidelines that improve discoverability and usability through practical, clig.dev-aligned documentation and reference resources.

Why do my Nushell CLI tools lack consistent interactive patterns?▼

Nushell CLI tools lack consistent interactive patterns without a cohesive playbook enforcing safe prompts, clear validation, and standardized configuration across commands, scripts, and plugins.

Related Skills

Explore More Software Engineering Skills→
mathruffian-dotmathruffian-dot
70

codex-env-setup

Set up Codex environments across desktop, CLI, and IDE extensions.

Community
Intermediate
tao3ktao3k
15

omniCell

Execute system commands and Nushell scripts, returning structured JSON results.

Official
Intermediate
ClankerGuruClankerGuru

gradle

Explain Gradle build lifecycle phases and configuration file roles.

Community
Advanced
newkayak12newkayak12
1

cli-developer

Develop CLI tools with argument parsing, prompts, and shell completions.

Community
Advanced