cmdop run

Execute a skill in one shot. No chat UI, no interactive turns — the skill runs, prints its output, exits with a non-zero code on failure. Designed for cron jobs, CI pipelines, and xargs-style fan-out.

Basic usage


cmdop run code-review src/
cmdop run check-services --machine vps-audi
cmdop run nightly-summary --output-format json

The first argument is the skill name (matched against builtin → global → workspace origins). Anything after is passed to the skill as arguments or appended to its prompt.

Targeting a remote machine


cmdop run check-services --machine prod-server
cmdop run disk-usage --machine vps-audi

The skill runs against the target machine’s environment — its files, processes, network. Internally this dispatches via ask_agent <host> so the remote machine’s permission gate applies.

Output formats


cmdop run nightly-summary --output-format json
cmdop run nightly-summary --output-format markdown
cmdop run nightly-summary --output-format text

JSON output includes structured fields (status, output, metrics) — useful for piping into jq or post-processing.

Difference from `cmdop chat`

cmdop run does not open a chat. It executes the skill, prints output, exits. For interactive use, run cmdop chat and pick the skill via the /skill <name> slash command.

	`cmdop run`	`cmdop chat`
TUI	No	Yes (in TTY)
Multi-turn	No	Yes
Exit code	Mirrors skill	0 on `/exit`
Best for	Cron, CI, scripts	Interactive operator

Listing available skills


cmdop skills list

See ./skills for skill management.

Combining with triggers

For scheduled execution, wire cmdop run into a trigger instead of an OS-level cron:


cmdop trigger add --name nightly-summary --schedule "0 3 * * *" \
  --skill nightly-summary --machine vps-audi

Triggers run on the daemon and surface failures into the Board. See ./trigger.

Exit behaviour

0 — skill completed successfully.
1 — skill ran but reported failure.
2 — invalid arguments / unknown skill.
6 — permission denied at the remote gate.