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

migrate-from-bland

Skill0 starsChanged 57 days agoMITView on GitHub

Import and validate Bland AI pathways or agents in ThunderPhone. Use when someone asks to migrate from Bland, create a Bland agent-import job, review pathway-node mappings, identify number or webhook gaps, commit selected imports, or compare source and ThunderPhone calls before cutover.

  • Reads credentials
  • Sends data out

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 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.

  • 3

    Very specific

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

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

    Choose a protected import mode: Use api_key only with authorized Bland access, or paste with a permitted export.

    line 16
  2. Very specific:

    Poll and review items: Read GET /v1/agent-imports/{public_id} until the item list is ready.

    line 53
  3. Very specific:

    Test matching paths: Use test-agent to traverse the same source pathway cases and ThunderPhone outcomes.

    line 63
  4. Distinctive:

    Use import agents and agent imports.

    line 82
  5. Distinctive:

    Never expose source credentials or infer phone-number transfer from agent creation.

    line 83
  6. Distinctive:

    Treat pathway conversion as behavior migration, not text copying.

    line 85

≈ “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 Bland

  1. Inventory the source. Export pathways/agents, nodes, prompts, numbers, tools, webhooks, credentials, traffic, and test cases. Record source versions before changing either platform.
  2. Choose a protected import mode. Use api_key only with authorized Bland access, or paste with a permitted export. Never persist source credentials in the import file or conversation.
  3. Create the job at POST /v1/agent-imports with source: bland.
{
  "source": "bland",
  "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-bland@1.0" --data-binary @bland-import.json
import json, os, requests
with open("bland-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-bland@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-bland@1.0" },
  body: await readFile("bland-import.json", "utf8") });
if (!r.ok) throw new Error(await r.text()); console.log(await r.json());
  1. Poll and review items. Read GET /v1/agent-imports/{public_id} until the item list is ready. Select and correct items with PATCH /v1/agent-imports/{public_id}/items/{item_id}.
  2. Review mapping. Prompt, first message, language, model, voice, supported tools, pathway-node content, and maximum duration can map. Owned numbers, webhooks, credentials, and unsupported pathway behavior need manual work. See references/bland-mapping.md.
  3. Commit reviewed selections with POST /v1/agent-imports/{public_id}/commit, poll to terminal, and record all created agent IDs. Delete an unwanted job before commit.
  4. Test matching paths. Use test-agent to traverse the same source pathway cases and ThunderPhone outcomes. Compare facts, branch outcomes, tools, transfer/end behavior, language, audio, and error recovery. Keep live number cutover separate and reversible.
  5. Use the current price index at https://thunderphone.com/data/voice-ai-price-index.json; do not invent comparison figures.

Errors

SymptomCauseFix
Pathway nodes collapse incorrectlySource graph has unsupported or ambiguous semanticsReconstruct the intent as general prompt/tool rules and test every path.
Agent imports without its numberNumbers are separate manual assetsProvision/connect and verify the number in a separate cutover plan.
Source webhooks stop workingVendor endpoint assumptions were copied incompletelyRebuild signed ThunderPhone webhooks and test deliveries before cutover.
Commit creates only some agentsSome review items were unselected or invalidInspect item states and errors; do not repeat the whole import blindly.

Source and safety rules

  • Use import agents and agent imports.
  • Never expose source credentials or infer phone-number transfer from agent creation.
  • Preserve source configuration and traffic until side-by-side evidence and rollback exist.
  • Treat pathway conversion as behavior migration, not text copying.

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.