<Stream> XML, the checks to run before the first call, and how to debug a call that fails. A skill is a set of instructions your agent loads on its own when the task matches, so you keep working the way you already do.
Install
The skill drives Plivo through the Plivo CLI. Install the CLI and log in first, or your agent falls back to raw API calls and loses the checks.
--global to install once for every project.
Any tool that follows the Agent Skills standard reads the same file.
Read it before you install
The skill is a plain Markdown file. Open it yourself, or give the URL to your agent.plivo-audio-streaming
The full skill file, published from this documentation site.
What is in the skill
What the agent does with it
- Checks readiness before writing code. The number is rented and voice-enabled, India compliance is accepted, the application has answer, fallback and hangup URLs, the answer URL returns valid
<Stream>XML, and your WebSocket answers. Read-only: nothing on your account changes. - Writes the XML for your case. Inbound or outbound, recording, a greeting, human handoff, status callbacks, using shapes that are known to work.
- Takes you to the first call in order, with a check at each step, so a failure is caught where it happens instead of on a live call.
- Debugs from evidence. It runs
plivo voice calls diagnose, reads the hangup cause, checks the XML, then tests the WebSocket, rather than guessing.
What it will not do
- It does not cover voice agents built on SIP platforms. Use the SIP trunking skill for LiveKit, ElevenLabs, Retell or Vapi.
- It does not cover XML beyond a streaming call. For IVRs, call routing, input collection or conferences, use the Voice XML skill.
- It does not cover SMS, WhatsApp or the browser SDK.
- It changes nothing on your account while checking. Anything that spends money or changes routing is shown to you first.
- It does not invent CLI flags or XML attributes. Where the documentation does not answer a question, it says so instead of guessing.
- It cannot see what Plivo cannot see, such as whether your server is deployed. It asks you.
Verify it is working
In the project where you installed it, ask your agent:
My caller hears silence after the call connects. My answer URL returns a <Stream>. What do I check?
You should get an ordered loop that starts with plivo voice calls diagnose <call_uuid> and the hangup cause, then the XML, then a WebSocket test. If you get generic WebSocket advice with no Plivo commands, the skill did not load.
Keeping it current
The published skill tracks this documentation. Your local copy does not update itself:Related
SIP trunking skill
For agents on LiveKit, ElevenLabs, Retell or Vapi
Voice XML skill
For IVRs, call routing, recording and conferences
Audio Streaming overview
How streaming works, without an agent
Plivo CLI
The command-line tool the skill drives