smithery/jeremylongshore

retellai-architecture-variants

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

Installation

$ npx skills add smithery/jeremylongshore --skill retellai-architecture-variants

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,068 B
  • docs SUMMARY.md 447 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Retell AI Architecture Variants

Overview

Implementation patterns for Retell AI architecture variants — 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 architecture variants

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

Choose a queue-backed architecture for bursty inbound calls

For a campaign that creates short spikes, keep the public number attached to a stable routing layer and place CRM enrichment behind an asynchronous queue. Start with a preview agent that records only synthetic test calls, set a clear timeout for the enrichment request, and configure a human-transfer fallback. Measure latency and transfer rate during the canary before selecting the variant for production traffic.

Resources

Next Steps

See related Retell AI skills for more workflows.