Oo Ably Control

Ably Control

Operate Ably Control through your OOMOL-connected account. This skill calls the ably_control connector with the 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 Control. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to 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:

oo connector schema "ably_control" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "ably_control" --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

• create_app — Create an Ably app in the connected account or supplied account ID. [write]
• create_key — Create an API key for an Ably app. [write]
• create_queue — Create a queue for an Ably app. [write]
• delete_app — Delete an Ably app by app ID. [destructive]
• delete_queue — Delete an Ably queue by queue ID. [destructive]
• get_account_stats — Retrieve account-level Ably statistics for the connected account or account ID.
• get_app_stats — Retrieve app-level Ably statistics for an Ably app.
• get_current_account — Retrieve the Ably Control API token, user, and account associated with the access token.
• list_apps — List Ably apps in the connected account or supplied account ID.
• list_keys — List API keys for an Ably app.
• list_queues — List queues for an Ably app.
• revoke_key — Revoke an Ably API key by key ID. [destructive]
• update_app — Update editable settings for an Ably app. [write]
• update_key — Update an Ably API key name or capability. [write]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Ably Control state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Ably Control is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  https://console.oomol.com/app-connections?provider=ably_control
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Ably Control homepage: https://ably.com