How do I install the CLI For Agent skill?

Run npx skillmds@latest add andersonlimahw/cli-for-agent in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CLI For Agent safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CLI For Agent?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CLI For Agent free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CLI For Agent?

Andersonlimahw (@andersonlimahw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CLI For Agent by andersonlimahw — Agent Skill

Name: CLI For Agent
Rating: 4.5 (4 reviews)
Author: Andersonlimahw

CLI For Agent

Design or review 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 agent-friendly CLIs.

File contents

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. Do not require arrow keys, menus, or timed prompts. If flags are missing, fall back to interactive — not the other way.

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.

`--help` That Works

Every subcommand has --help. Every --help includes Examples with real invocations.

Options:
  --env     Target environment (staging, production)
  --tag     Image tag (default: latest)
  --force   Skip confirmation

Examples:
  mycli deploy --env staging
  mycli deploy --env production --tag v1.2.3

Stdin, Flags, and Pipelines

Accept stdin where it makes sense. Avoid odd positional ordering. Support chaining.

Fail Fast With Actionable Errors

On missing required flags: exit immediately with a clear message and a correct example invocation.

Error: No image tag specified.
  mycli deploy --env staging --tag <image-tag>

Idempotency

Agents retry often. The same successful command run twice should be safe (no-op or explicit "already done").

Destructive Actions

Add --dry-run so agents can preview plans. Offer --yes / --force to skip confirmations.

Predictable Structure

Use consistent patterns: resource + verb. If mycli service list exists, mycli deploy list should follow the same shape.

Success Output

Return machine-useful data on success: IDs, URLs, durations.

deployed v1.2.3 to staging
url: https://staging.myapp.com
deploy_id: dep_abc123

---name: cli-for-agentdescription: Design or review 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 agent-friendly CLIs.---# CLI for AgentsHuman-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 FirstEvery input should be expressible as a flag. Do not require arrow keys, menus, or timed prompts. If flags are missing, fall back to interactive — not the other way.**Bad:** `mycli deploy` → `? Which environment? (use arrow keys)`**Good:** `mycli deploy --env staging`## Discoverability Without Dumping ContextAgents discover subcommands incrementally: `mycli`, then `mycli deploy --help`. Do not print the entire manual on every run.## `--help` That WorksEvery subcommand has `--help`. Every `--help` includes **Examples** with real invocations.```Options: --env Target environment (staging, production) --tag Image tag (default: latest) --force Skip confirmationExamples: mycli deploy --env staging mycli deploy --env production --tag v1.2.3```## Stdin, Flags, and PipelinesAccept stdin where it makes sense. Avoid odd positional ordering. Support chaining.## Fail Fast With Actionable ErrorsOn missing required flags: exit immediately with a clear message and a correct example invocation.```Error: No image tag specified. mycli deploy --env staging --tag <image-tag>```## IdempotencyAgents retry often. The same successful command run twice should be safe (no-op or explicit "already done").## Destructive ActionsAdd `--dry-run` so agents can preview plans. Offer `--yes` / `--force` to skip confirmations.## Predictable StructureUse consistent patterns: `resource` + `verb`. If `mycli service list` exists, `mycli deploy list` should follow the same shape.## Success OutputReturn machine-useful data on success: IDs, URLs, durations.```deployed v1.2.3 to stagingurl: https://staging.myapp.comdeploy_id: dep_abc123```

Frequently asked questions