voice-call-app

Automate voice-call workflows by steering UI and triggering spawn_live_audio.

2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/lovon-spec/intendant --skill voice-call-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: voice-call-app
Source: https://github.com/lovon-spec/intendant/tree/main/skills/voice-call-app
Command: npx skills add https://github.com/lovon-spec/intendant --skill voice-call-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automating voice-call workflows across desktop apps to reduce manual navigation and ensure consistent, auditable live-audio sessions.

Core Features & Use Cases

  • UI-driven call initiation across apps (Element, FaceTime, WhatsApp) with AI-assisted guidance
  • Integration with spawn_live_audio to manage live-audio sessions and return structured results
  • Prerequisite checks and permission handling (Vortex Audio plugin, mic access, GUI session)

Quick Start

Initiate a voice call by selecting a target app and triggering the spawn_live_audio workflow with a prepared playbook.

Frequently Asked Questions about voice-call-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate voice calls across desktop apps?

Automate voice calls by steering the UI across apps like FaceTime or WhatsApp and triggering spawn_live_audio to produce structured results. It requires a macOS or Linux GUI session, Vortex Audio HAL plugin, and mic permission.

Can I initiate a FaceTime or WhatsApp call using AI agent GUI automation?

Yes, AI-assisted GUI automation initiates voice calls across apps like FaceTime and WhatsApp. You select a target app and trigger the spawn_live_audio workflow with a prepared playbook to manage the session.

What prerequisites do I need to run live-audio session automation on macOS?

Live-audio automation on macOS requires a GUI session, the Vortex Audio HAL plugin, microphone access permissions, and the target voice-call app installed and logged in before triggering the workflow.

Does voice-call automation require a specific response schema for AI agents?

Yes, voice-call automation requires a defined response_schema, timeout_secs, and an id field to satisfy integration requirements. The workflow returns a LiveAudioResult containing the structured data payload.

Why does my voice-call workflow fail to return structured audio results?

Voice-call workflows fail if prerequisite checks are unmet, such as missing mic permissions, lacking the Vortex Audio HAL plugin, or no active GUI session on macOS or Linux to execute the UI-driven automation.

What is the best way to manage UI-driven call initiation and live-audio sessions?

The best way to manage UI-driven call initiation is integrating AI control with spawn_live_audio to handle live-audio sessions. This approach reduces manual navigation and ensures consistent, auditable results.