smithery/jeremylongshore

retellai-upgrade-migration

Retell AI upgrade migration \u2014 AI voice agent and phone call automation.\n\ Use when working with Retell AI for voice agents, phone calls, or telephony.\nTrigger\ \ with phrases like \"retell upgrade migration\", \"retellai-upgrade-migration\"\ , \"voice agent\".\n"

Installation

$ npx skills add smithery/jeremylongshore --skill retellai-upgrade-migration

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/jeremylongshore · top by installs.

npx skills add smithery/jeremylongshore

Browse all from smithery/jeremylongshore

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.9.0
LicenseMIT
CompatibilityDesigned for Claude Code
Allowed toolsRead, Write, Edit, Bash(npm:*), Bash(curl:*), Grep
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,076 B
  • docs SUMMARY.md 368 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Retell AI Upgrade Migration

Overview

Implementation patterns for Retell AI upgrade migration — voice agent and telephony platform.

Prerequisites

  • Completed retellai-install-auth setup

Instructions

Step 1: SDK Pattern

import Retell from 'retell-sdk';
const retell = new Retell({ apiKey: process.env.RETELL_API_KEY! });

const agents = await retell.agent.list();
console.log(`Agents: ${agents.length}`);

Output

  • Retell AI integration for upgrade migration

Error Handling

Error Cause Solution
401 Unauthorized Invalid API key Check RETELLAPIKEY
429 Rate Limited Too many requests Implement backoff
400 Bad Request Invalid parameters Check API documentation

Examples

Upgrade an SDK through a compatibility canary

Pin the candidate SDK version in a branch and run the development agent suite against synthetic create-call, retrieval, error, and webhook scenarios. Record the old and new package versions and any changed request shapes, then deploy a preview configuration before altering production dependencies. Keep the prior lockfile and agent version available until the canary has met its error and latency limits, so rollback does not require reconstructing the old runtime.

Resources

Next Steps

See related Retell AI skills for more workflows.