Manage OOMOL Console data through the oo CLI, using live action schemas and safeguards for changes that affect teams, permissions, and account settings.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install oo-oomol-console
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install oo-oomol-console using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is OOMOL Console?
The OOMOL Console skill lets an AI agent read and manage account, team, Connection, permission, billing, and usage information through the OOMOL connector and the oo CLI. OOMOL injects credentials server-side, so the workflow avoids handling raw access tokens.
As one of the Openclaw Skills for OOMOL Console tasks, it directs the agent to inspect an action’s authoritative live schema before preparing a request. Reads can run directly, while write and destructive actions require user confirmation appropriate to their impact.
OOMOL Console Use Cases
- Check the authenticated account’s current team scope, team metadata, or member list.
- Review team Connections, Connection execution records, or permission groups.
- Inspect account balances, billing summaries, and daily usage breakdowns.
- Add a member to the current team after confirming the intended change.
- Create, update, or delete Connection permission groups with explicit approval for destructive changes.
- Update the default permission group for a Connection after reviewing the action schema and confirming the overwrite.
- Investigate an OOMOL Console request by checking CLI installation, sign-in status, or insufficient-credit errors when a command fails.
How OOMOL Console Works
- Identify the OOMOL Console action that matches the request.
- Retrieve the action’s current input and output contract with
oo connector schemabefore constructing a payload. - Determine whether the action is a read, write, or destructive operation. Confirm the exact payload and effect with the user for writes; get explicit approval for destructive actions.
- Run the action through the
oomol_consoleconnector usingoo connector run, supplying a JSON payload that conforms to the live schema. - Review the returned
dataand, when useful, the execution identifier atmeta.executionId. - If the command fails because the CLI is missing or the account is not signed in, follow the matching one-time setup step. Do not initiate sign-in proactively.
OOMOL Console Setup
The skill assumes that the oo CLI is installed and signed in. Do not run oo auth login unless an action fails with an authentication error. Install or sign in only when needed:
# macOS / Linux: install the oo CLI if the command is missing
curl -fsSL https://cli.oomol.com/install.sh | bash
# Sign in once if an action reports an authentication error
oo auth login
For Windows PowerShell, install with:
irm https://cli.oomol.com/install.ps1 | iex
Inspect an action schema and run it with a JSON payload:
oo connector schema "oomol_console" --action "<action_name>"
oo connector run "oomol_console" --action "<action_name>" --data '<json>' --json
--data accepts a JSON object string or a path such as @path/to/file.json; omit it to send {}. If a request fails with HTTP 402 or OOMOL_INSUFFICIENT_CREDIT, recharge the account at https://console.oomol.com/billing/token-recharge before retrying.
OOMOL Console Data Schema & Taxonomy
The skill does not define a local database or generate persistent files by default. It sends action-specific JSON input to the oomol_console connector and returns the connector response.
| Data area | Available information and operations |
|---|---|
| Account and teams | Current scope and principal, visible teams, team summary, members, and member addition |
| Connections | Visible team Connections and Connection execution records |
| Connection permissions | Default and custom permission groups; create, update, or delete custom groups; update the default group |
| Billing and usage | Balance lots, compact billing metrics, and daily usage by source and subject |
| Request and response | Input fields come from the live action schema; the response has data and meta.executionId |
When providing input from a file, pass its path through --data using the @path/to/file.json form. The action schema—not a static field list—defines the authoritative payload contract.
OOMOL Console Advanced Features
- Live schema discovery for each action helps ensure payloads match the current connector contract.
- Covers read operations as well as team-member, Connection, and permission-group management.
- Uses explicit safety tiers: reads are safe to run directly, writes require user confirmation, and destructive changes require explicit approval.
- Returns an execution identifier at
meta.executionIdfor tracing an action. - Avoids handling raw tokens because OOMOL injects credentials server-side.
- Provides conditional, one-time recovery steps for a missing CLI, authentication errors, and insufficient account credit.
SKILL.md
Loading
Related Openclaw Skills
Greip Network Lookup
Query Greip for IP address, autonomous system, and country information through the oo CLI without handling API tokens.
Nationalize
Use Nationalize through OOMOL to predict likely country candidates and probabilities from one name or a batch of up to 100 names.
Easy-Peasy.AI
Connect an AI coding agent to Easy-Peasy.AI to inspect text-generation presets and create text through a credential-managed oo CLI workflow.
Xingpan API
Access Xingpan astrology data through OOMOL’s oo CLI to calculate charts, explore compatibility, and retrieve horoscopes without handling API credentials.
Wisburg Research Connector
Use this Openclaw Skills integration to search and retrieve Wisburg research, reports, articles, and market updates through the oo CLI.
Dynalist
A secure Dynalist integration for reading, creating, updating, organizing, and deleting outlines through the OOMOL-connected oo CLI.
Featured*
