managing-rundesklisted
Install: claude install-skill rundesk-ai/rundesk-cli
# Manage Rundesk
Use Rundesk's commands to answer questions about this install. Do not guess at its state or paths.
## Use the right install
Run `"$RUNDESK_COMMAND"`, never bare `rundesk`. It is the absolute command for the install running
this turn. `$RUNDESK_HOME` already points to that install; do not change it or introduce another
location.
```sh
"$RUNDESK_COMMAND" status
"$RUNDESK_COMMAND" --help
```
Treat generated help as authoritative. If a verb is absent, Rundesk cannot perform it. A command
exits `0` when it answered or completed, `1` when understood but not completed, and `2` for invalid
command syntax. Never report success from wording alone; read the exit code and result.
## Common entry points
| Priority | Need | Command |
|---|---|---|
| 1 | Prove which install this is and whether it is healthy | `"$RUNDESK_COMMAND" status` |
| 2 | See the agents and their providers | `"$RUNDESK_COMMAND" agents` |
| 3 | See whether gateways are running | `"$RUNDESK_COMMAND" gateways` |
| 4 | Explain gateway trouble | `"$RUNDESK_COMMAND" gateways logs <agent>` |
| 5 | Check provider, channel, and skill readiness | `"$RUNDESK_COMMAND" providers check <provider>` · `"$RUNDESK_COMMAND" channels doctor <agent>` · `"$RUNDESK_COMMAND" skills doctor <agent>` |
| 6 | Protect approved risky work | `"$RUNDESK_COMMAND" backups save` |
Choose the narrowest command that answers the request. Before a mutation, inspect only enough state
to identify the exact target and consequence. Mos