smithery/jeremylongshore

retellai-known-pitfalls

Retell AI known pitfalls \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 known pitfalls\", \"retellai-known-pitfalls\", \"voice\ \ agent\".\n"

Installation

$ npx skills add smithery/jeremylongshore --skill retellai-known-pitfalls

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,035 B
  • docs SUMMARY.md 403 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Retell AI Known Pitfalls

Overview

Implementation patterns for Retell AI known pitfalls — 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 known pitfalls

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

Avoid a duplicate-call retry after a network timeout

An outbound request times out after submission. Before retrying, look up the request correlation or call identifier to determine whether Retell already created the call. If state is unknown, hold the retry and escalate with the redacted request metadata; sending a second request can contact the same person twice. Add bounded retries only where the operation is explicitly idempotent and monitor the duplicate-call rate after the change.

Resources

Next Steps

See related Retell AI skills for more workflows.