ClawHub

Voice AI Agent Engineering

v1.0.0

Design, build, and deploy production-grade AI voice agents for calls, covering conversation design, voice UX, telephony integration, and scalable platform-ag...

⭐ 0· 82·0 current·0 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description claim a methodology for voice agent design and deployment; the SKILL.md contains templates, decision trees, architecture diagrams, and vendor recommendations that match that purpose. There are no unrelated environment variables, binaries, or install steps requested.
✓
Instruction Scope
Runtime instructions are limited to design guidance, YAML templates, architecture/latency rules, compliance checklists, and vendor comparisons. The instructions do not direct the agent to read system files, environment variables, or to transmit data to unexpected endpoints. They do recommend integrating with external platforms (Twilio, Deepgram, ElevenLabs, LLM providers), which is appropriate for the topic but will require separate credentials and code when implemented.
✓
Install Mechanism
No install spec and no code files — instruction-only. This is the lowest-risk install mechanism; nothing is downloaded or written to disk by the skill itself.
✓
Credentials
Skill declares no required env vars, no primary credential, and no config paths. Recommendations reference third-party services, but the skill does not request or attempt to access those credentials. Expect that any real implementation based on these instructions will require service keys (telephony, STT, TTS, LLM) obtained separately.
✓
Persistence & Privilege
No 'always: true' privilege and default autonomous invocation is allowed (normal for skills). The skill does not request persistent system presence or make changes to other skills or system-wide configs.
Assessment
This is a methodology/playbook (no code, no installs, no credentials), so installing it itself is low-risk and consistent with its stated purpose. Before you act on the recommendations: (1) Vet and provision any telephony/STT/TTS/LLM keys separately and follow least-privilege practices (rotate keys, use separate accounts/environments); (2) Get legal/compliance review for TCPA, HIPAA, PCI, and regional privacy laws before running automated or outbound voice agents; (3) When you implement code or use third-party SDKs named in the guide, inspect those packages and download them from official release channels (avoid unknown URLs); (4) Treat the external links and paid 'context packs' as third-party content—review them before paying or installing. Overall the skill is internally coherent and matches its description.

Like a lobster shell, security has layers — review code before you run it.

agentvk979nef6rr19tb68t5ae9zswex83hf86aivk979nef6rr19tb68t5ae9zswex83hf86call-centervk979nef6rr19tb68t5ae9zswex83hf86latestvk979nef6rr19tb68t5ae9zswex83hf86phonevk979nef6rr19tb68t5ae9zswex83hf86sttvk979nef6rr19tb68t5ae9zswex83hf86telephonyvk979nef6rr19tb68t5ae9zswex83hf86ttsvk979nef6rr19tb68t5ae9zswex83hf86twiliovk979nef6rr19tb68t5ae9zswex83hf86vapivk979nef6rr19tb68t5ae9zswex83hf86voicevk979nef6rr19tb68t5ae9zswex83hf86

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments