cli-agent-onboard

Build a reusable CLI environment profile with runtime, binary, flags, and config.

5|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/cli-agent-spec/cli-agent-spec --skill cli-agent-onboard-cli-agent-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-agent-onboard
Source: https://github.com/cli-agent-spec/cli-agent-spec/tree/main/skills/cli-agent-onboard
Command: npx skills add https://github.com/cli-agent-spec/cli-agent-spec --skill cli-agent-onboard-cli-agent-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates unreliable AI-agent interactions with CLI tools by automatically building a verified environment profile that captures how the CLI should be invoked non-interactively.

Core Features & Use Cases

  • Reads agent-facing documentation: Ingests AGENTS.md, CODING_AGENTS.md, and README.md to learn expected invocation, environment variables, and non-interactive conventions.
  • Detects runtime and resolves the exact binary: Identifies the project type (Python/Node/Rust/Go) from manifests and verifies the executable via --version or --help.
  • Discovers non-interactive flags and config: Scans --help output for prompt-suppression and output-format flags, and records relevant configuration env vars.
  • Stores a reusable environment profile: Writes evaluations/<cli-name>/environment.md for reuse by cli-agent-evaluate and related skills.

Quick Start

Run cli-agent-onboard with the target CLI command so it creates evaluations/<cli-name>/environment.md containing the OS, runtime/toolchain, resolved binary, non-interactive flags, and config requirements.

Frequently Asked Questions about cli-agent-onboard

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

FAQPage Schema
How do I profile a CLI tool for non-interactive execution by AI agents?

To profile a CLI for non-interactive execution, you need to detect its runtime, resolve the exact binary, and discover prompt-suppression flags. This creates a verified environment profile that prevents agents from hanging on interactive prompts.

How do I detect the correct binary and runtime for a Python, Node, Rust, or Go CLI?

Detect the correct binary and runtime for Python, Node, Rust, or Go CLIs by reading project manifests and agent-facing documentation like AGENTS.md. You then verify the resolved executable using --version or --help to ensure reliable invocation.

Does this CLI onboarding approach work across macOS, Linux, and Windows environments?

Yes, this CLI onboarding approach works across macOS, Linux, and Windows environments. It profiles the OS and runtime toolchain to resolve the invocable binary, ensuring reliable agent runs regardless of the underlying operating system.

What's the best way to discover non-interactive flags and configuration environment variables for a CLI?

The best way to discover non-interactive flags and configuration environment variables is to scan the --help output. Combined with reading README.md and CODING_AGENTS.md, this captures the necessary output-format flags and config requirements.

Why does my AI agent fail to run a CLI tool when the runner prefix is not obvious?

Your AI agent fails when the runner prefix is not obvious because it cannot resolve the exact executable. Building an environment profile resolves the binary name and runner prefix from manifests, verifying invocation before the agent attempts execution.

Where should I store the environment profile for a CLI tool so evaluation pipelines can reuse it?

Store the environment profile for a CLI tool in evaluations/<cli-name>/environment.md. This file persists the OS, resolved binary, non-interactive flags, and config requirements so downstream evaluation pipelines can reliably reuse the verified invocation data.