cli-for-agents
Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.
Install
git clone https://github.com/cursor/plugins /tmp/plugins && ln -s /tmp/plugins/cli-for-agent/skills/cli-for-agents ~/.claude/skills/cli-for-agentsFrom README
CLI for agents Human-oriented CLIs often block agents: interactive prompts, huge upfront docs, and help text without copy-pasteable examples. Prefer patterns that work headlessly and compose in pipelines. Non-interactive first Every input should be expressible as a flag or flag value. Do not require arrow keys, menus, or timed prompts. If flags are missing, then fall back to interactive mode—not the other way around. Bad: mycli deploy → ? Which environment? (use arrow keys) Good: mycli deploy --env staging Discoverability without dumping context Agents discover subcommands incrementally: mycli, then mycli deploy --help. Do not print the entire manual on every run. Let each subcommand own its documentation so unused commands stay out of context. --help that works Every subcommand has --help. Every --help includes Examples with real invocations. Examples do more than prose for pattern-matching. stdin, flags, and pipelines Accept stdin where it makes sense (e.g.
More from this repo
thermos
Launch both thermo-nuclear review subagents in parallel, then synthesize their findings.
continual-learning
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.
check-compiler-errors
Used to run compile and type-check commands and report failures