oo-ablylisted

# Ably Operate **Ably** through your OOMOL-connected account. This skill calls the `ably` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens. ## Running an action Assume the user has already installed the oo CLI, signed in, and connected Ably. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error. **1. Inspect the contract** to get the authoritative input/output schema before building a payload: ```bash oo connector schema "ably" --action "<action_name>" ``` **2. Run the action** with a JSON payload that matches the input schema: ```bash oo connector run "ably" --action "<action_name>" --data '<json>' --json ``` - `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`. - The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`. Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields. ## Available actions - `batch_presence` — Query current presence for multiple Ably channels. - `batch_presence_history` — Query presence history for multiple Ably channe