Individual skill
voice-agent-design
Design a safe, vendor-neutral voice agent with conversation flows, consent notices, escalation paths, and approval-gated actions. Use for: voice agent design, phone assistant, call flow, conversational IVR.
.grok/skills/voice-agent-design/SKILL.md
Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- grok Repository topic
- prompt-engineering Repository topic
- workflow-automation Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Voice Agent Design
## Purpose
Design a voice-agent specification that is concise, understandable, and safe for callers. The skill is vendor-neutral and does not assume a specific telephony or model provider.
## Workflow
1. Define the agent’s purpose, audience, supported tasks, and explicit exclusions.
2. Draft a short conversation flow: greeting, disclosure where appropriate, intent capture, information gathering, resolution, confirmation, and close.
3. Identify sensitive data, recording notices, retention rules, and a path to a human representative.
4. List every external action, such as booking, messaging, payment, or account change, and require explicit confirmation immediately before it occurs.
5. Define failure handling for uncertainty, silence, interruption, bad transfer, and urgent or sensitive topics.
6. Write a test plan covering normal, ambiguous, adversarial, and escalation calls.