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

migrate-from-retell

Skill0 starsChanged 57 days agoMITView on GitHub

Import and validate Retell AI agents in ThunderPhone. Use when someone asks to migrate from Retell, create a Retell agent-import job, review response-engine or flow mappings, identify manual tool and number work, commit selected items, or run parity tests 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, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Choose api_key or paste mode: Use direct access only with an authorized source credential.

    line 16
  2. Very specific:

    Poll and edit review items: Use GET /v1/agent-imports/{public_id}, then PATCH /v1/agent-imports/{public_id}/items/{item_id} for selection, …

    line 54
  3. Distinctive:

    Use import agents and the agent-import API.

    line 84
  4. Distinctive:

    Do not claim feature parity from a successful commit alone.

    line 86
  5. Distinctive:

    Keep traffic changes, number moves, and credential revocation outside the review import.

    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 Retell

  1. Inventory the source. Export agents, response engines or flow states, numbers, tools, knowledge, webhooks, credentials, traffic, and test cases. Record the source revision and unresolved ownership before any import.
  2. Choose api_key or paste mode. Use direct access only with an authorized source credential. Keep that credential in the protected request flow; never put it in logs, prompts, or committed JSON.
  3. Create the job with POST /v1/agent-imports, source: retell, and the selected auth mode.
{
  "source": "retell",
  "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-retell@1.0" --data-binary @retell-import.json
import json, os, requests
with open("retell-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-retell@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-retell@1.0" },
  body: await readFile("retell-import.json", "utf8") });
if (!r.ok) throw new Error(await r.text()); console.log(await r.json());
  1. Poll and edit review items. Use GET /v1/agent-imports/{public_id}, then PATCH /v1/agent-imports/{public_id}/items/{item_id} for selection, name, voice, product, or prompt choice.
  2. Check mapping and gaps. General/global prompts, flow state content, supported tools, transfer/end/DTMF, voice, language, model, knowledge, voicemail, silence, keywords, and duration can map. Numbers, webhooks, credentials, custom engines, SMS tools, and vendor MCP settings need manual review. See references/retell-mapping.md.
  3. Commit reviewed items with POST /v1/agent-imports/{public_id}/commit; poll to terminal and record the created IDs. Delete an abandoned uncommitted job explicitly.
  4. Run matched side-by-side tests with test-agent. Verify every flow transition, DTMF/tool action, knowledge result, transfer, language, audio, and end condition. Traffic cutover and source retirement are separate, approval-gated work with rollback.
  5. Use live comparison data from https://thunderphone.com/data/voice-ai-price-index.json; never invent or freeze a competitor rate in the skill.

Errors

SymptomCauseFix
Response engine is incompleteCustom engine or flow construct is unsupportedPreserve the source and rewrite the behavior as reviewed prompt/tool logic.
DTMF or tool action differsVendor action schema did not map exactlyRebuild and test the action with explicit inputs and success evidence.
Import auth failsRetell access or auth mode is invalidUse a correctly scoped credential or permitted paste payload.
Tests are not comparableSource and destination scenarios/config differFreeze the case set and record both revisions and environments.

Source and safety rules

  • Use import agents and the agent-import API.
  • Protect source credentials and preserve unmodified source assets until cutover is verified.
  • Do not claim feature parity from a successful commit alone.
  • Keep traffic changes, number moves, and credential revocation outside the review import.

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.