From rust
Guides building Rust CLI apps with clap argument parsing, anyhow error context, progress bars, signal handling, exit codes, and subprocess testing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rust:cliThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Argument parsing, user-facing output, exit codes, signal handling, and subprocess testing for command-line tools.
Argument parsing, user-facing output, exit codes, signal handling, and subprocess testing for command-line tools.
Activate when:
anyhow::Context to an error chain for a readable top-level failure messageFor argument parsing, error context, output, signals, exit codes, and testing patterns, see references/cli.md.
use clap::Parser;
#[derive(Parser)]
struct Cli {
pattern: String,
path: std::path::PathBuf,
}
fn main() {
let cli = Cli::parse(); // derives parsing, validation, and --help
}
The full argument-parsing, error-context, output, signals, exit-code, and testing patterns are in references/cli.md.
This skill covers CLI-specific ecosystem crates. For custom error enum design (thiserror) shared with non-CLI code, see rust:error-handling. For unit and integration test structure not specific to CLI binaries, see rust:testing.
See /core:anti-fabrication — crate versions and behavior claims in this skill are verified against crates.io and the upstream Rust CLI Book, not assumed.
2plugins reuse this skill
First indexed Jul 19, 2026
npx claudepluginhub vinnie357/claude-skills --plugin rustGuides building Rust CLI apps with clap argument parsing, anyhow error context, progress bars, signal handling, exit codes, and subprocess testing.
Guides building CLI tools in Rust with argument parsing via clap, config layering, progress bars, terminal UI, and user communication patterns.
Guides Rust development for CLI tools, backend services, and application code using Cargo workspaces, axum, clap, and tooling like clippy, rustfmt, and cargo-nextest.