Zoomies — скилл

---
name: zoomies
description: Look after a Zoomies self-hosted GitHub Actions runner fleet from a coding agent. Check its health, find out why a job failed or is waiting, and read or change pools, hosts and runners, with the zoomies command or its MCP tools. Use when the user asks about their Zoomies fleet, self-hosted runners, queued or failed CI jobs, pools, hosts or capacity. Not for editing workflow files, and not for changing GitHub itself (use gh).
---

# Zoomies

Zoomies runs a fleet of ephemeral GitHub Actions runners on the user's own
machines. This skill is for asking that fleet questions and, when the user says
so, changing it. Everything it needs is the `zoomies` command or the Zoomies MCP
tools; there is no other way in, and neither can do more than the token behind
it.

## Where each question goes

| The question is about | Use |
| --- | --- |
| The live fleet: jobs, queue, pools, hosts, runners, capacity, what is wrong | `zoomies`, or the Zoomies MCP tools when they are connected |
| GitHub itself: a workflow run, a pull request, a repository setting | `gh`, not Zoomies |
| A workflow file in a repository | Read the file. The `zoomies-kennel` skill checks it for what Kennel Club looks at, and `zoomies-optimise` works out why a job is slow and which preview fits; both are separate installs that the person makes, with the command in the project's README |
| Installing, configuring or upgrading Zoomies | The documentation at https://zoomies.sh, and the user's own hands |

## Preflight

Run `zoomies status` before anything else. It names the controller when all is
well. When the Zoomies MCP tools are connected instead, `fleet_status` is the
same check and the command is not needed. When it does not, stop and say which of these it is, and do not try other
commands to get round it:

* **Not installed.** The shell says `command not found`. Tell the user; do not
  install anything unasked.
* **Not set up.** `no controller URL`. Ask the user for the controller's address.
  They set it with `ZOOMIES_URL`, `--url`, or `url:` in
  `~/.config/zoomies/cli.yaml`.
* **Not signed in.** The controller rejected the request (401), or the token's
  role is not enough (403). The user makes a token with `zoomies tokens create`
  and sets `ZOOMIES_TOKEN` themselves; never ask for a token to be pasted into
  the conversation.
* **Not reachable.** `cannot reach the controller`. The address is wrong, the
  controller is down, or something blocks the port.

## Reading the fleet

Ask for `--output json` whenever you will read the result yourself, and
`--help` on any command for its flags and an example. The complete list of