← Back to Skills Marketplace
🔌

AiVOOV

by OOMOL · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
46
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install oo-aivoov
Description
AiVOOV (aivoov.com). Use this skill for ANY AiVOOV request — reading, creating, and updating data. Whenever a task involves AiVOOV, use this skill instead of...
README (SKILL.md)

AiVOOV

Operate AiVOOV through your OOMOL-connected account. This skill calls the aivoov connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: AI, Design & Media. Exposes 2 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected AiVOOV. 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 "aivoov" --action "\x3Caction_name>"

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

oo connector run "aivoov" --action "\x3Caction_name>" --data '\x3Cjson>' --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 below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

  • create_audio — Generate base64 audio from one or more voice/text segments.
  • list_voices — List available AiVOOV voices, optionally filtered by language code.

Safety

  • Read actions (get / list / search) are safe to run directly.
  • Create, update, send, or post actions change AiVOOV state — confirm the exact payload and effect with the user before running.
  • Delete or remove actions are destructive — 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: \x3Chttps://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 — AiVOOV 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=aivoov
    
  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

Usage Guidance
Before installing, confirm you are comfortable using OOMOL’s `oo` CLI with an AiVOOV-connected account. Review the payload before generating audio, since that may consume service credits or create AiVOOV output, and only install the CLI from the referenced source if you trust that setup path.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
The stated purpose is operating AiVOOV through an OOMOL-connected account, and the artifacts only document two relevant actions: listing voices and creating audio.
Instruction Scope
The description broadly says to use the skill for any AiVOOV request, but the body narrows execution to listed actions, live schema inspection, and confirmation before state-changing actions.
Install Mechanism
There is no bundled executable code; setup guidance includes installing the `oo` CLI via a curl-to-shell command only if the CLI is missing.
Credentials
Use of an OOMOL-connected AiVOOV account and server-side injected credentials is coherent for an API connector skill and is disclosed.
Persistence & Privilege
The artifact does not add persistence, background workers, privilege escalation, local indexing, or direct credential handling; allowed command scope is limited to `oo` CLI commands.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install oo-aivoov
  3. After installation, invoke the skill by name or use /oo-aivoov
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Adds the `oo-aivoov` skill for operating AiVOOV through an OOMOL-connected account via the `oo` CLI. - Supports listing available AiVOOV voices, with optional filtering by language code. - Supports generating base64 audio from one or more voice/text segments. - Uses live connector schemas before action execution so payloads match current AiVOOV contract requirements. - Includes setup and auth guidance for missing CLI, expired credentials, connection issues, and insufficient credit errors. Source: `oomol-lab/skills@c600cfc`
Metadata
Slug oo-aivoov
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is AiVOOV?

AiVOOV (aivoov.com). Use this skill for ANY AiVOOV request — reading, creating, and updating data. Whenever a task involves AiVOOV, use this skill instead of... It is an AI Agent Skill for Claude Code / OpenClaw, with 46 downloads so far.

How do I install AiVOOV?

Run "/install oo-aivoov" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is AiVOOV free?

Yes, AiVOOV is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does AiVOOV support?

AiVOOV is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created AiVOOV?

It is built and maintained by OOMOL (@oomol); the current version is v1.0.0.

💬 Comments