voice-workflow-agent-kit v1.0
Price: $4.99
Category: automation
What it does
voice-workflow-agent-kit turns call transcripts, intake notes, or JSON case snippets into practical starter assets for voice-agent operations. It identifies customer intent, urgency, suggested next actions, and escalation needs, then generates a workflow specification, case summary, and handoff template your team can adapt before connecting live voice or customer channels.
The skill is designed for teams prototyping support, sales, casework, and back-office voice workflows without needing external voice APIs or complex setup.
Use cases
- Support teams that want to convert real call examples into repeatable intake, triage, escalation, and handoff flows.
- Sales operators building voice-assisted demo, quote, upgrade, or qualification workflows from sample conversations.
- Back-office and casework teams that need structured summaries, audit-friendly handoffs, and clear next-owner templates for phone-led processes.
Requirements
- OpenClaw: compatible with standard AgentSkill execution in OpenClaw v2026.3.23+.
- Runtime: Python 3.9+.
- Dependencies: Python standard library only; no pip packages required.
- API keys: none.
- Inputs: a plain-text transcript/notes file or JSON containing
cases,text, ortranscriptfields.
Example usage
python scripts/voice_workflow_agent_kit.py \
--input calls.txt \
--workflow support \
--output-dir voice-kit \
--company "Acme Support" \
--json
Expected output
Console summary:
{
"artifacts": [
"workflow-spec.json",
"case-summary.md",
"handoff-template.md"
],
"cases_analyzed": 3,
"high_urgency": 1,
"output_dir": "voice-kit"
}
Generated files:
workflow-spec.json— workflow stages, guardrails, analyzed cases, intents, urgency, actions, and escalation flags.case-summary.md— human-readable case-by-case summary for review.handoff-template.md— reusable handoff format covering caller need, verified facts, actions taken, risk/escalation, next owner, and customer-safe summary.
QA and security notes
Viper QA on 2026-04-27 passed 6/6 tests. Warlock security audit cleared the release: no eval/exec/subprocess usage, no hardcoded keys, no network calls, and no external voice API calls observed.