Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From retellai-pack
Provides implementation patterns for Retell AI architecture variants including voice agents and telephony automation. Use when building AI voice agent systems or phone call workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/retellai-pack:retellai-architecture-variantsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implementation patterns for Retell AI architecture variants — voice agent and telephony platform.
Implementation patterns for Retell AI architecture variants — 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 |
See related Retell AI skills for more workflows.
npx claudepluginhub pw00kt/fuzzy-sniffle --plugin retellai-pack2plugins reuse this skill
First indexed Jul 18, 2026
Provides implementation patterns for Retell AI architecture variants including voice agents and telephony automation. Use when building AI voice agent systems or phone call workflows.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.