voice-agents▌
casper-studios/casper-marketplace · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Create ElevenLabs Conversational AI voice agents for client discovery, feedback, and check-in calls. Automatically generates agent configuration from client context.
Voice Agents
Overview
Create ElevenLabs Conversational AI voice agents for client discovery, feedback, and check-in calls. Automatically generates agent configuration from client context.
Quick Decision Tree
What type of agent?
│
├── Discovery agent (interview clients)
│ └── --scope discovery
│
├── Feedback agent (post-project)
│ └── --scope feedback
│
├── Check-in agent (relationship)
│ └── --scope check-in
│
├── Qualification agent (leads)
│ └── --scope qualification
│
└── Onboarding agent (new contacts)
└── --scope onboarding
Environment Setup
# Required in .env
ELEVENLABS_API_KEY=your_api_key
OPENROUTER_API_KEY=your_api_key # For prompt generation
Common Usage
Create Discovery Agent
python scripts/create_voice_agent.py "Microsoft" --scope discovery --notes "CRM migration project"
Create Feedback Agent
python scripts/create_voice_agent.py "Acme Corp" --scope feedback --notes "Post-project review"
Dry Run (Preview)
python scripts/create_voice_agent.py "Test Company" --scope discovery --notes "Testing" --dry-run
Scope Types
| Scope | Purpose |
|---|---|
discovery |
Interview client team about operations, pain points, tech stack |
feedback |
Gather feedback on completed project |
check-in |
Periodic relationship check-ins |
qualification |
Qualify inbound leads before sales |
onboarding |
Guide new contacts through info gathering |
Generated Agent Config
The script generates:
Agent Name
[{Company Name}] {Scope} Agent v1
First Message
Voice-optimized greeting that:
- Introduces as calling on behalf of Casper Studios
- Confirms speaking with right person
- States purpose aligned with scope
- Sets time expectations (10-15 minutes)
- Asks for confirmation
System Prompt
Comprehensive conversation guide with:
- Identity and context
- Tone and communication style
- Conversation flow (5-7 stages)
- Interviewing techniques
- Guardrails and boundaries
Output
{
"agent_id": "abc123xyz",
"agent_name": "[Microsoft] Discovery Agent v1",
"agent_url": "https://elevenlabs.io/app/conversational-ai/agents/abc123xyz",
"first_message": "Hi there! This is an AI assistant...",
"company_name": "Microsoft",
"scope": "discovery"
}
Context Enrichment
The script optionally fetches context from Google Drive:
- Client's "Research" document
- Previous meeting transcripts (intro calls)
If not available, generates with provided notes only.
Cost
| Service | Cost |
|---|---|
| OpenRouter (prompt generation) | ~$0.01-0.03 |
| ElevenLabs agent creation | Free |
| Google Drive | Free |
Security Notes
Credential Handling
- Store
ELEVENLABS_API_KEYin.envfile (never commit to git) - Store
OPENROUTER_API_KEYin.envfile (never commit to git) - Regenerate keys from respective dashboards if compromised
- Never log or print API keys in script output
Data Privacy
- Voice agents conduct live conversations with customers
- Call content may include sensitive business discussions
- Agent prompts may contain internal business context
- Conversation logs are stored by ElevenLabs
- Client context from Google Drive may be included in prompts
Access Scopes
ELEVENLABS_API_KEY- Full access to voice agent creation/managementOPENROUTER_API_KEY- AI model access for prompt generation- Google OAuth - Optional, for client context enrichment
Compliance Considerations
- Recording Consent: Inform callers that conversations may be recorded
- AI Disclosure: Disclose that caller is speaking with an AI agent
- Caller Privacy: Conversation data is processed by ElevenLabs servers
- GDPR: EU caller conversations require appropriate consent
- TCPA/CCPA: Comply with applicable telecommunications regulations
- Call Recording Laws: Recording laws vary by jurisdiction (one-party vs two-party consent)
- Data Retention: Review ElevenLabs data retention policies
- Agent Guardrails: Ensure agents have appropriate conversation boundaries
Troubleshooting
Common Issues
Issue: Agent creation failed
Symptoms: API error when creating voice agent Cause: Invalid configuration, missing fields, or API issue Solution:
- Validate agent config JSON format
- Ensure all required fields are present (name, first_message, system_prompt)
- Check prompt length doesn't exceed limits
- Review ElevenLabs API documentation for requirements
Issue: Invalid voice ID
Symptoms: "Voice not found" or "invalid voice_id" error Cause: Voice ID doesn't exist or not accessible Solution:
- Use valid ElevenLabs voice ID from your library
- Check voice availability at https://elevenlabs.io/app/voice-library
- Verify voice is not a custom voice from another account
- Use default voice if custom voice unavailable
Issue: API quota exceeded
Symptoms: "Quota exceeded" or rate limit error Cause: ElevenLabs subscription limits reached Solution:
- Check usage at https://elevenlabs.io/app/subscription
- Upgrade subscription tier for more capacity
- Reduce number of concurrent agents
- Delete unused agents to free up slots
Issue: Agent not responding in calls
Symptoms: Agent created but doesn't respond in conversations Cause: System prompt issues, webhook configuration, or service issue Solution:
- Test agent directly in ElevenLabs console first
- Review system prompt for clear instructions
- Check webhook URL is accessible (if configured)
- Verify ElevenLabs service status
Issue: OpenRouter prompt generation failed
Symptoms: Error generating agent prompt Cause: OpenRouter API issue or invalid model Solution:
- Verify
OPENROUTER_API_KEYis set correctly - Check model availability at OpenRouter
- Try a different model if current one unavailable
- Run with
--dry-runto test without API calls
Issue: Google Drive context not loading
Symptoms: Agent created without client context Cause: OAuth issue or client folder not found Solution:
- Verify Google OAuth credentials (see google-workspace skill)
- Check client folder exists in expected location
- Provide context via
--notesflag as alternative - Run without context enrichment first to isolate issue
Resources
- references/elevenlabs.md - ElevenLabs API details
Integration Patterns
Context-Aware Agents
Skills: transcript-search → voice-agents Use case: Create voice agents with client history Flow:
- Search transcript-search for past client meetings
- Extract relationship history, pain points, and preferences
- Include context in voice agent system prompt for personalized conversations
Agent Notes to CRM
Skills: voice-agents → attio-crm Use case: Log voice agent call summaries Flow:
- Voice agent completes discovery or feedback call
- Extract call summary, insights, and action items
- Create note on Attio company record with call details
Research-Enriched Agents
Skills: parallel-research → voice-agents Use case: Arm voice agents with company intelligence Flow:
- Run parallel-research on target company
- Extract recent news, funding, tech stack, and pain points
- Include research in agent prompt for informed conversations
How to use voice-agents on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add voice-agents
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches voice-agents from GitHub repository casper-studios/casper-marketplace and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate voice-agents. Access the skill through slash commands (e.g., /voice-agents) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★46 reviews- ★★★★★Aanya White· Dec 24, 2024
voice-agents has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Yuki Anderson· Dec 12, 2024
Keeps context tight: voice-agents is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Dec 4, 2024
voice-agents has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Oshnikdeep· Nov 23, 2024
Keeps context tight: voice-agents is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Diego Sharma· Nov 15, 2024
Keeps context tight: voice-agents is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Camila Shah· Nov 3, 2024
voice-agents has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Hana Patel· Oct 22, 2024
voice-agents fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ganesh Mohane· Oct 14, 2024
We added voice-agents from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Aanya Kim· Oct 6, 2024
We added voice-agents from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Olivia Thomas· Sep 25, 2024
Registry listing for voice-agents matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 46