yo-protocol-clilisted

ALWAYS use this skill when the user mentions the YO Protocol CLI, the `yo` command, `@yo-protocol/cli`, or wants to interact with YO Protocol vaults (yoETH, yoUSD, yoBTC, yoEUR, yoGOLD, yoUSDT) from a shell script, terminal, or command line. The `yo` binary is an agent-first interface for ERC-4626 yield vaults on Ethereum (1), Base (8453), and Arbitrum (42161). It outputs structured JSON to stdout, never requires or accepts private keys, and produces unsigned calldata routed through the YO Gateway — ready for Safe/AA wallets and Base MCP `send_calls`. Use it for: building unsigned transactions (`yo prepare {approve,deposit,redeem,deposit-with-approval}`), reading positions and rewards (`yo position`, `yo portfolio`, `yo pending-redeems`, `yo rewards`, `yo yo-rewards`, `yo user-perf`), listing vaults and history (`yo vaults`, `yo vault`, `yo history`, `yo prices`, `yo yield`, `yo tvl`, `yo share-price`, `yo perf`, `yo leaderboard`), self-describing the command surface for an agent (`yo schema`), setting up `YO
yoprotocol/yo-protocol-skills · ★ 1 · AI & Automation · score 71

Install: claude install-skill yoprotocol/yo-protocol-skills

Official YO Protocol skill. Canonical repository: <https://github.com/yoprotocol/yo-protocol-skills>. # YO Protocol CLI — Reference Agent-first interface for YO Protocol ERC-4626 vaults. Outputs JSON to stdout, errors to stderr. **Never requires or accepts private keys.** Designed for agents, bots, scripts, Safe/AA wallets, and Base MCP `send_calls`. **Canonical source for the command surface is `yo schema`** — this file documents the same surface but `yo schema` is authoritative. If a command appears here but not in `yo schema`, trust the schema. ## Installation ```bash npm install -g @yo-protocol/cli # or run on demand without installing npx @yo-protocol/cli@latest <command> ``` Binary: `yo` (or `npx yo`). npm: <https://www.npmjs.com/package/@yo-protocol/cli>. ## Global options Every command inherits these. The `--json` flag is **required for agent use** — without it, output is interactive/text and not parseable. | Flag | Description | Default | Env | | ----------------- | -------------------------------------------------------------- | ------- | ------------ | | `--rpc-url <url>` | RPC endpoint for on-chain reads | public | `YO_RPC_URL` | | `--chain <id>` | Chain ID: `1` (Ethereum), `8453` (Base), or `42161` (Arbitrum) | `1` | — | | `--json` | Force JSON output (agent compat). **Use on every agent call.** | off | — | |