executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
retellai-local-dev-loopRetell AI local dev loop — AI voice agent and phone call automation. Use when working with Retell AI for voice agents, phone calls, or telephony. Trigger with phrases like "retell local dev loop", "retellai-local-dev-loop", "voice agent".
Independent GitHub snapshot · Automated classification · Original documentation governs
name: retellai-local-dev-loop
description: "Retell AI local dev loop \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 local dev loop", "retellai-local-dev-loop", "voice
\ agent".\n"
allowed-tools: Read, Write, Edit, Bash(npm:), Bash(curl:), Grep
version: 1.9.0
license: MIT
author: Jeremy Longshore jeremy@intentsolutions.io
tags:
Implementation patterns for Retell AI local dev loop — voice agent and telephony platform.
retellai-install-auth setupimport 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}`);
| Error | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Invalid API key | Check RETELL_API_KEY |
| 429 Rate Limited | Too many requests | Implement backoff |
| 400 Bad Request | Invalid parameters | Check API documentation |
Keep a small suite of synthetic caller intents, including a successful request, an unclear request, and a required human handoff. Run that suite against a development agent after each prompt or tool-schema change and compare only redacted outcomes such as route, tool arguments, and completion state. Do not point local development at a production phone number; publish a versioned preview only after the suite continues to meet its expected behavior.
See related Retell AI skills for more workflows.