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-security-basicsRetell AI security basics — 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 security basics", "retellai-security-basics", "voice agent".
Independent GitHub snapshot · Automated classification · Original documentation governs
name: retellai-security-basics
description: "Retell AI security basics \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 security basics", "retellai-security-basics", "
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 security basics — 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 |
Disable the exposed development key in the provider console, create a scoped replacement, and update only the development secret reference. Verify the new key with a harmless agent-list request while ensuring command output does not print its value. Review access logs and affected preview configurations, then document the incident with the credential identifier and rotation time rather than copying key material into the ticket or source repository.
See related Retell AI skills for more workflows.