Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Create, manage, and deploy ElevenLabs conversational AI agents. Use when the user wants to work with voice agents, list their agents, create new ones, or manage agent configurations.
Create, manage, and deploy ElevenLabs conversational AI agents. Use when the user wants to work with voice agents, list their agents, create new ones, or manage agent configurations.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Manage ElevenLabs conversational AI agents on behalf of the user. Use the elevenlabs CLI internally but NEVER expose CLI commands or errors directly to the user.
Hide CLI details: Never tell users to run commands. Handle everything silently. Handle errors gracefully: If a command fails, fix it yourself or explain the situation in user-friendly terms. Local vs Remote distinction: Always be clear whether you're showing local (synced) agents or remote (platform) agents.
Run these checks silently before attempting any agent operation:
elevenlabs auth whoami If not authenticated, tell the user: "You're not logged into ElevenLabs. I'll need your API key to continue." Then run elevenlabs auth login and guide them through it.
Look for agents.json in the working directory. If missing, silently run: elevenlabs agents init Never tell the user about missing agents.json - just initialize.
When user asks to see their agents: First try elevenlabs agents list (shows local agents) If no local agents exist, tell user: "You have no local agents synced. Would you like me to pull your agents from ElevenLabs?" If they confirm, run elevenlabs agents pull then list again Present results in a clean table/list format, not raw CLI output
When user wants to create an agent: Ask for agent name and purpose (don't mention "templates") Based on their description, choose appropriate template: Customer support β customer-service General assistant β assistant Voice-focused β voice-only Simple/minimal β minimal Default for unclear cases β default Run: elevenlabs agents add "Name" --template <template> Inform user the agent was created locally Ask: "Would you like me to deploy this to ElevenLabs now?" If yes, run elevenlabs agents push
Pull (remote β local): elevenlabs agents pull # all agents elevenlabs agents pull --agent <id> # specific agent elevenlabs agents pull --update # overwrite local with remote Tell user: "I've synced your agents from ElevenLabs." Push (local β remote): elevenlabs agents push --dry-run # preview first, check for issues elevenlabs agents push # actual push Tell user: "I've deployed your changes to ElevenLabs."
elevenlabs agents status Present as: "Here's the sync status of your agents:" followed by a clean summary.
When user wants to add integrations/tools: Ask what the tool should do Ask for the webhook URL or configuration Create config file and run: elevenlabs agents tools add "Tool Name" --type webhook --config-path ./config.json Push changes: elevenlabs agents push
elevenlabs agents widget <agent_id> Present the HTML snippet cleanly, explain where to paste it.
Instead of saying...Say..."Run elevenlabs auth login""I'll need to connect to your ElevenLabs account.""No agents.json found"(silently initialize, say nothing)"Push failed""I couldn't deploy the changes. Let me check what went wrong...""You have 0 agents""You don't have any agents synced locally. Want me to check ElevenLabs for existing agents?""Agent created locally""I've created your agent. Would you like to deploy it now?"
After initialization, the working directory contains: agents.json - Agent registry agent_configs/ - Agent configuration files tools.json - Tool registry tool_configs/ - Tool configurations These are implementation details - don't mention them to users unless they specifically ask about project structure.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.