Update to ThunderPhone

{
  "description": "Move ElevenLabs agents to ThunderPhone without sharing a ElevenLabs key in chat. Use when someone asks to migrate or import from ElevenLabs, review what an import mapped, or finish an import.",
  "included_files": [],
  "name": "migrate-from-elevenlabs",
  "skill_md_contents": "---\nname: migrate-from-elevenlabs\ndescription: Move ElevenLabs agents to ThunderPhone without sharing a ElevenLabs key in chat. Use when someone asks to migrate or import from ElevenLabs, review what an import mapped, or finish an import.\nlicense: MIT\ncompatibility: Requires the ThunderPhone MCP server, connected with OAuth. No step asks for a password, API key or other secret.\nmetadata:\n  author: thunderphone\n  version: \"1.0\"\n---\n\n# Migrate from ElevenLabs\n\n1. **Start in the dashboard.** Call `start_agent_import` with platform `elevenlabs`\n   and give the user its `web_url`. They enter their ElevenLabs API key there,\n   never in chat. If they paste a key into the chat, do not use it, and suggest\n   they rotate it.\n2. **Follow the import** with `get_agent_import`. Show each ElevenLabs agent\n   with its mapped name, voice, tier and warnings. The warnings name what did\n   not carry over; plan those with the user.\n3. **Finish after a yes** with `commit_agent_import`, choosing `item_ids` when the\n   user wants only some. It runs in the background; check `get_agent_import`\n   again for the new agent ids.\n4. **Test before switching traffic.** Run `test_in_text` and `test_my_agent` on\n   each new agent, then move numbers only when the user is happy.\n\nDocs: https://thunderphone.com/docs/guides/import-agents\n"
}