cli-anything

Wrap command-line tools into agent skills with documented invocation and error contracts.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill cli-anything-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-anything
Source: https://github.com/coco-research/coco/tree/main/skills/cli-anything
Command: npx skills add https://github.com/coco-research/coco --skill cli-anything-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a command-line tool into a reliable agent skill so an AI can invoke it predictably, read its results, and handle failures without guessing.

Core Features & Use Cases

  • CLI Introspection: Captures real help output, subcommands, flags, positional arguments, and exit behavior before documenting the tool.
  • Structured Output Contract: Defines how an agent should read machine-friendly results, including JSON output when available or precise stdout parsing when not.
  • Error Contract: Documents parseable failure behavior so agents can distinguish success from actionable errors.
  • Use Case: Convert a third-party utility, internal binary, or developer tool into a skill that an assistant can call safely and consistently.

Quick Start

Ask the AI to inspect your CLI, verify its real behavior, and write a SKILL.md wrapper that documents its invocation, outputs, and errors.

Frequently Asked Questions about cli-anything

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

FAQPage Schema
How do I make a command-line tool callable by an AI agent?

To make a CLI tool callable by an AI agent, you wrap it with an agent-facing interface that documents exact invocations, parses stdout or JSON results, and defines explicit error contracts. This ensures predictable execution without guessing.

What is CLI introspection for agent integration?

CLI introspection for agent integration captures a tool's real help output, subcommands, flags, and exit behavior before generating a wrapper. This observed behavior ensures the agent receives accurate invocation details and structured documentation.

How do I handle CLI errors when an AI agent invokes a command?

To handle CLI errors during AI agent invocation, you define an error contract that documents parseable failure behavior. This allows the agent to distinguish successful executions from actionable errors and respond appropriately.

Can I convert a human-only CLI tool into a structured agent skill?

Yes, you can convert a human-only CLI tool into a structured agent skill by verifying its exact invocation details and defining a structured output contract. This involves precise stdout parsing or utilizing available JSON output for machine-friendly results.

What information do I need before wrapping a CLI tool for agent use?

Before wrapping a CLI tool for agent use, you need observed help output, exact invocation details, explicit result and error contracts, and verified examples. This prerequisite information guarantees the wrapper accurately reflects the tool's real behavior.