cli-tooling-engineering
v0.1.4CLI-tooling-engineering team — agents (cli-architect, cli-implementation-engineer, tui-engineer, cli-distribution-engineer) for command-line tools and TUIs that feel native to the shell: the command/subcommand + flag/positional surface, config precedence (flags > env > file > default), the output contract (human by default, --json on demand, exit codes as an API, data->stdout/diagnostics->stderr, NO_COLOR/TTY detection), stdin, signal handling, TUIs (Ink / Bubble Tea / Textual / ratatui) with a non-TTY fallback, shell completions, and distribution (single static binary, Homebrew / Scoop / winget / npm / pipx, --version + update path). skills, a knowledge bank (command-surface + output/exit-code + framework + distribution decision trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Seams: service logic -> backend-engineering, release/signing -> devops-cicd, GUI sibling -> desktop-app-engineering, docs -> technical-writing-docs. Requires ravenclaude-core@>=0.7.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install cli-tooling-engineering for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install cli-tooling-engineering@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/cli-tooling-engineering/.
Plugin files
├── .claude-plugin/plugin.json├── skills/cli-design-and-arg-parsing/SKILL.md├── skills/cli-distribution-and-packaging/SKILL.md├── skills/output-and-exit-code-contract/SKILL.md├── skills/shell-completions-and-config/SKILL.md└── skills/tui-design/SKILL.md
Included Skills5
Design a CLI's command/subcommand surface, flags vs positionals, and config precedence (flags > env > file > default), then pick the idiomatic parser for the language. Use when starting a CLI or reworking a messy one.
Plan how a CLI ships and updates — single static binary vs runtime package, cross-compilation, install channels (Homebrew/Scoop/winget/npm/pipx), a build-stamped --version, and a safe installer. Use when making a tool installable and keeping it current.
Define a CLI's output contract — human by default, --json on demand, data to stdout, diagnostics to stderr — and an exit-code map treated as a public API. Use when a tool must serve both humans and scripts, or CI keeps passing on real failures.
Generate shell completions (bash/zsh/fish/PowerShell) from the parser and design config-file discovery + env-var conventions (XDG, TOOL_* prefixes). Use when adding tab completion or a config/env layer to a CLI.
Decide whether a full-screen TUI is warranted (vs a scriptable CLI), pick the framework (Ink / Bubble Tea / Textual / ratatui), and design the render-loop + non-TTY fallback. Use for interactive terminal dashboards, pickers, and wizards.
Plugin manifests1
{
"name": "cli-tooling-engineering",
"version": "0.1.4",
"description": "CLI-tooling-engineering team — agents (cli-architect, cli-implementation-engineer, tui-engineer, cli-distribution-engineer) for command-line tools and TUIs that feel native to the shell: the command/subcommand + flag/positional surface, config precedence (flags > env > file > default), the output contract (human by default, --json on demand, exit codes as an API, data->stdout/diagnostics->stderr, NO_COLOR/TTY detection), stdin, signal handling, TUIs (Ink / Bubble Tea / Textual / ratatui) with a non-TTY fallback, shell completions, and distribution (single static binary, Homebrew / Scoop / winget / npm / pipx, --version + update path). skills, a knowledge bank (command-surface + output/exit-code + framework + distribution decision trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Seams: service logic -> backend-engineering, release/signing -> devops-cicd, GUI sibling -> desktop-app-engineering, docs -> technical-writing-docs. Requires ravenclaude-core@>=0.7.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"cli",
"command-line",
"tui",
"argument-parsing",
"subcommands",
"exit-codes",
"stdout-stderr",
"json-output",
"shell-completions",
"single-binary",
"no-color",
"stdin"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.7.0"
]
},
"lspServers": "./.lsp.json"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[cli-tooling-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/cli-tooling-engineering)