vapi

Translate Vapi voice events into standardized dashboard templates.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/gracebotly/flowetic-app --skill vapi-gracebotly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vapi
Source: https://github.com/gracebotly/flowetic-app/tree/main/workspace/skills/vapi
Command: npx skills add https://github.com/gracebotly/flowetic-app --skill vapi-gracebotly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mapping guidance for Vapi voice events to dashboard templates, enabling consistent analytics and faster visualization.

Core Features & Use Cases

  • Provides mapping heuristics to align common voice-metrics (duration, status, cost) with standardized dashboard fields.
  • Supports a reusable template reference (voice-analytics) for consistent dashboards across projects.
  • Use Case: When a dataset of Vapi voice events arrives with duration, status, and cost, apply the mapping to produce ready-for-dashboard inputs.

Quick Start

Create a mapping from a sample Vapi voice event to the voice-analytics dashboard template.

Frequently Asked Questions about vapi

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

FAQPage Schema
How do I map Vapi voice events to a dashboard template?

Yes, you can use the voice-analytics template reference to ensure consistent visualization of Vapi voice events across multiple projects by aligning common metrics with standardized dashboard fields.

What are the mapping heuristics for Vapi voice analytics duration and cost?

Mapping heuristics for Vapi voice events work by aligning common voice metrics like duration, status, and cost with standardized dashboard fields, enabling consistent analytics and faster visualization.

How do I visualize Vapi call cost and duration in a standardized dashboard?

Standardized dashboard fields for Vapi voice events include duration, status, and cost, which are aligned using mapping heuristics to ensure consistent analytics across different dashboards.

Can I use the voice-analytics template for Vapi events across different projects?

To start mapping Vapi voice events, create a mapping from a sample voice event containing duration, status, and cost to the standardized voice-analytics dashboard template fields.

Do I need raw Vapi voice event metrics to use the dashboard mapping?

The best way to generate ready-for-dashboard inputs from Vapi calls is to apply the predefined mapping heuristics to raw voice events, referencing the voice-analytics template for consistent visualization.

Are there limitations when mapping Vapi voice events to standardized fields?

Limitations of mapping Vapi voice events include the restriction to duration, status, and cost metrics; events lacking these specific metrics may not map correctly to the standardized dashboard template.