Update to ElevenLabs

{
  "name": "agents-platform",
  "description": "Manage ElevenLabs voice agents through the connected ElevenLabs MCP server. Use when the user asks to create, configure, test, deploy, or inspect agents, knowledge bases, agent tools, tests, or conversations directly on their ElevenLabs account — rather than writing application code. Requires the ElevenLabs MCP server bundled with this plugin.",
  "included_files": [],
  "skill_md_contents": "---\nname: agents-platform\ndescription: Manage ElevenLabs voice agents through the connected ElevenLabs MCP server. Use when the user asks to create, configure, test, deploy, or inspect agents, knowledge bases, agent tools, tests, or conversations directly on their ElevenLabs account — rather than writing application code. Requires the ElevenLabs MCP server bundled with this plugin.\nlicense: MIT\n---\n\n# ElevenLabs Agents Platform (via MCP)\n\nWorkflow guidance for the `agents_*` tools on the ElevenLabs MCP server. Every\ntool takes a `context` parameter — briefly state the user's goal in it. For\nbuilding agents in the user's own codebase (SDK, CLI, widget embedding), use the\ngeneral `agents` skill instead.\n\n## Creating and updating agents\n\n- Create with `agents_create` using the top-level fields (`name`, `prompt`,\n  `first_message`, `voice_id`, `language`, `tags`). Only reach for the raw\n  `body` escape hatch when a field has no top-level equivalent. `voice_id` is\n  optional — the workspace default voice is used if omitted.\n- Before changing an existing agent, read it: `agents_list` to find it,\n  `agents_get` to see its current config, then `agents_update` with only the\n  fields that should change.\n- `agents_duplicate` clones an existing agent — prefer it over recreating a\n  config by hand.\n- Get a shareable/test link with `agents_get_link`; inspect widget config with\n  `agents_get_widget`.\n\n## Knowledge base\n\n- Add documents with `agents_create_kb_url` (supports auto-sync for pages that\n  change) or `agents_create_kb_text`; organize with `agents_create_kb_folder`.\n- Before deleting a document, check `agents_get_kb_dependents` — other agents\n  may use it. Confirm with the user before `agents_bulk_delete_knowledge_base`.\n- Verify retrieval quality with `agents_query_knowledge_base_rag` or\n  `agents_search_knowledge_base` after adding documents.\n\n## Testing and deployment\n\n- Create tests with `agents_create_test`: an LLM response test\n  (`success_condition` prompt plus success/failure examples), a tool-call test\n  (verify a tool was or wasn't called with expected parameters), or a\n  simulation test (`simulation_scenario` persona plus `success_conditions`).\n- Run and inspect with `agents_list_test_runs` / `agents_get_test_run`.\n- For staged changes, branch: `agents_create_branch`, make edits, preview with\n  `agents_merge_branch_preview`, then `agents_merge_branch` and\n  `agents_create_deployment`.\n\n## Conversations\n\n- `agents_list_conversations` and `agents_get_conversation` inspect call\n  history and transcripts; `agents_search_conversation_messages` finds\n  specific exchanges. Use these to debug agent behavior before editing prompts.\n\n## Safety\n\n- Confirm with the user before destructive calls: `agents_delete`,\n  `agents_delete_tool`, `agents_delete_phone_number`, knowledge-base bulk\n  deletes. Deletions are not reversible.\n- IDs (agent, document, tool, branch) only ever come from tool results — never\n  guess or reconstruct them.\n"
}