← ClaudeAtlas

gemini-omnilisted

Create Gemini Omni voice resources, character resources, and text-to-video tasks through RunAPI. Use when the user asks an agent to create or manage Gemini Omni audio voices, character resources, or multimodal video. Default to the RunAPI CLI for one-off calls; use SDKs only when integrating RunAPI into an app or backend.
runapi-ai/gemini-omni · ★ 0 · AI & Automation · score 76
Install: claude install-skill runapi-ai/gemini-omni
# Gemini Omni On RunAPI Create Gemini Omni voice resources, character resources, and text-to-video tasks through RunAPI. The default path for one-off agent tasks is the `runapi` CLI; SDKs are for application integration. ## Routing decision - One-off voice, character, or video generation for the user → use the **CLI path** with the `runapi` binary. - Building an app, backend, worker, library, or production codebase → use the **SDK integration path**. ## Variants - Audio: create reusable voice resources with `runapi gemini-omni create-audio`. - Character: create reusable character resources with `runapi gemini-omni create-character`. - Video: create text-to-video tasks with `runapi gemini-omni text-to-video`. ## CLI path The `runapi` binary is the runtime dependency. Run `runapi auth status` first. For agents and headless runs, prefer `RUNAPI_API_KEY` or import it into saved config. Inspect the available commands and request fields with CLI help: ```shell runapi gemini-omni --help runapi gemini-omni create-audio --help runapi gemini-omni create-character --help runapi gemini-omni text-to-video --help ``` Run a one-off request: ```shell runapi gemini-omni create-audio --input-file request.json ``` For video tasks, submit asynchronously and wait for completion: ```shell runapi gemini-omni text-to-video --async --input-file request.json runapi wait <task-id> --service gemini-omni --action text-to-video ``` Available commands: `create-audio`, `create-character`, `tex