agentleFS
thunderphonethunderphone/skills/migrate-from-elevenlabs/SKILL.md

migrate-from-elevenlabs

Skill0 starsChanged 58 days agoMITView on GitHub

Import and validate ElevenLabs conversational agents in ThunderPhone. Use when someone asks to migrate from ElevenLabs Agents, create an ElevenLabs import job, review voice or knowledge mappings, identify client-tool or MCP gaps, commit selected items, or run side-by-side calls before cutover.

  • Reads credentials
  • Sends data out

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Choose import mode: Use authorized api_key discovery or a permitted paste payload.

    line 16
  2. Distinctive:

    Run side-by-side tests: Use identical scenarios for source and ThunderPhone.

    line 66
  3. Distinctive:

    Use import agents and the agent-import API.

    line 85
  4. Distinctive:

    Never expose source secrets or assume a source voice exists in ThunderPhone.

    line 86
  5. Distinctive:

    Keep source agents and traffic intact until matched tests and rollback are complete.

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Migrate from ElevenLabs

  1. Inventory the source. Export conversational agents, prompts, first messages, voices, LLM settings, tools, knowledge, numbers, secrets, traffic, and test cases. Record the source version and content owners.
  2. Choose import mode. Use authorized api_key discovery or a permitted paste payload. Keep the source credential in the protected API flow and out of prompts, JSON files, output, and logs.
  3. Create the job at POST /v1/agent-imports with source: elevenlabs.
{
  "source": "elevenlabs",
  "auth_mode": "paste",
  "payload": "${EXPORTED_AGENT_JSON}"
}
curl --fail-with-body -X POST https://api.thunderphone.com/v1/agent-imports \
  -H "Authorization: Bearer $THUNDERPHONE_API_KEY" -H "Content-Type: application/json" \
  -H "X-ThunderPhone-Client: skills/migrate-from-elevenlabs@1.0" --data-binary @elevenlabs-import.json
import json, os, requests
with open("elevenlabs-import.json", encoding="utf-8") as f: payload = json.load(f)
r = requests.post("https://api.thunderphone.com/v1/agent-imports", json=payload,
    headers={"Authorization": f"Bearer {os.environ['THUNDERPHONE_API_KEY']}",
             "X-ThunderPhone-Client": "skills/migrate-from-elevenlabs@1.0"}, timeout=60)
r.raise_for_status(); print(r.json())
import { readFile } from "node:fs/promises";
const r = await fetch("https://api.thunderphone.com/v1/agent-imports", { method: "POST",
  headers: { Authorization: `Bearer ${process.env.THUNDERPHONE_API_KEY}`,
    "Content-Type": "application/json",
    "X-ThunderPhone-Client": "skills/migrate-from-elevenlabs@1.0" },
  body: await readFile("elevenlabs-import.json", "utf8") });
if (!r.ok) throw new Error(await r.text()); console.log(await r.json());
  1. Poll and review items. Fetch GET /v1/agent-imports/{public_id} until ready; use PATCH /v1/agent-imports/{public_id}/items/{item_id} to select and correct each candidate.
  2. Review mapping. Prompt, first message, language, LLM choice, voice, webhook tools, supported system tools, knowledge, silence, and maximum duration can map. Numbers, secret values, client-side tools, MCP servers, and unsupported vendor capabilities need manual work. See references/elevenlabs-mapping.md.
  3. Commit only reviewed items with POST /v1/agent-imports/{public_id}/commit; poll to terminal and record each created ID. Discard an uncommitted job with DELETE /v1/agent-imports/{public_id}.
  4. Run side-by-side tests. Use identical scenarios for source and ThunderPhone. Compare tool and knowledge evidence, transfer/end behavior, language, pronunciation, interruption, audio, and latency. Create a separate approved plan for numbers, traffic, and source retirement.
  5. Read current comparison data from https://thunderphone.com/data/voice-ai-price-index.json; do not publish invented or stale rates.

Errors

SymptomCauseFix
Voice does not mapSource voice is unavailable or incompatibleSelect a real voice returned by GET /v1/voices and evaluate it in audio.
Client tool disappearsBrowser/client-executed tools are not server toolsRebuild an authorized server integration or keep the client layer explicitly.
Knowledge answers differSource documents or retrieval behavior did not transfer fullyImport permitted sources, run direct search, then test spoken answers.
MCP capability is missingRemote MCP servers are manual assetsRegister them through /v1/mcp-servers, review discovered tools, and attach deliberately.

Source and safety rules

  • Use import agents and the agent-import API.
  • Never expose source secrets or assume a source voice exists in ThunderPhone.
  • Keep source agents and traffic intact until matched tests and rollback are complete.
  • Separate transcript similarity from audio, latency, connection, and tool evidence.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.