Cate CLI
Read this skill before the first `cate` command, the CLI on PATH in every Cate terminal...
Install
npx skills add 0-AI-UG/cate --skill cate-cli -g -a claude-code -y- Repository
- 0-AI-UG/cate2.2k
- Category
- Testing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,230 tokens
- Runs scripts
- No, instructions only
What it does
Read this skill before the first `cate` command, the CLI on PATH in every Cate terminal (CATE_SOCKET and CATE_TOKEN are set) that drives the workspace the terminal belongs to. Use it whenever a task in a Cate terminal needs Cate itself, even if the person never mentions the CLI, such as looking at, testing or signing in to a web page in Cate's browser panel, taking a screenshot, reading or typing into another terminal, opening a file or panel for the person, starting other coding agents in their own panels or worktrees and waiting for their answers, or recording findings in a Review panel. It covers targeting panels, CLI permissions, and the browser and agent workflows. It is not for working on Cate's own source code, and not for theming Cate, which has the cate-theme skill.
Cate CLI
cate talks to the workspace's runtime over the local socket named by
CATE_SOCKET, authenticated by CATE_TOKEN, a per-terminal token that also
names the calling panel. It works the same when the workspace lives on
another machine. If either variable is missing, cate exits 3 and says so:
you are not in a Cate terminal, so this skill does not apply.
Reference files
Read the one for your task before its first command:
references/browser.md: the browser panel. Snapshots and element ids, clicking and typing, tabs, uploads, dialogs, saved logins and sign-ups, console and network logs, screenshots.references/agents.md: starting other coding agents, sending them prompts, waiting for and reading their answers, and typing into terminals that have no agent.
Panels, terminals, editors and Review panels are covered below.
Permissions
Each area needs its permission in the workspace's Settings → CLI: the master switch "Command-line control (cate CLI)" plus a Read and a Control cell per area (Browser, Browser passwords, Terminal, Panels, Files, Agents & reviews). Sending keystrokes to terminals (Terminal, Control) and using saved browser passwords are off by default. A denied call fails with an error naming the setting: tell the person which one to turn on instead of working around it.
Help, output and exit codes
The CLI's own help is the reference for exact syntax. Check it before guessing a flag:
cate --help # command groups and global flags
cate panel --help # the commands of one group (or just: cate panel)
cate review note add --help # one command: arguments, flags and defaults
A mistyped command suggests the closest one. Lists print as aligned tables,
other results as key value lines, structured reports as indented JSON.
Add --json to any command when you parse the result or need full ids.
Every error says what to do next.
