Operon CLI Ops

Use this skill for operational inspection and scriptable CLI workflows. Prefer JSON output for automation:

operon --config <path> --json config explain
operon --config <path> --json doctor
operon --config <path> --json node list
operon --config <path> --json capability list <node>

For exact flags, run the relevant help command first:

operon --help
operon doctor --help
operon config explain --help
operon node --help
operon capability --help
operon audit show --help
operon trace --help
operon run --help

Common scenarios:

• Need to know which config is active: operon config explain.
• Need first-pass troubleshooting for config, endpoint, auth, protocol, capability, or service health: operon doctor.
• Need to see reachable configured nodes: operon node list, then operon node ping <node>.
• Need LAN mDNS endpoint discovery: operon node discover --timeout-secs 3.
• Need to know what a node allows: operon capability list <node>.
• Need evidence for a change: operon audit show <node> with filters such as capability, action, allowed, resource, or limit.
• Need execution graph evidence: run a graph with operon run <workflow.yaml> --trace-output <trace.json>, then inspect with operon trace show <trace.json>.

For scripts, validate that --json produces one JSON document before piping it into downstream tools. Use --quiet only when the command result is represented by exit status or a side effect.