create-workflow

Build visual node-based workflows for deterministic Vapi conversations.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ostsam/vapight-kampff --skill create-workflow-ostsam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-workflow
Source: https://github.com/ostsam/vapight-kampff/tree/main/.agents/skills/create-workflow
Command: npx skills add https://github.com/ostsam/vapight-kampff --skill create-workflow-ostsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build robust, multi-step voice and chat conversations by visually composing deterministic workflows with node-based components. Automates consistent handling of branching, tool execution, and handoffs to reduce prompt drift and runtime errors.

Core Features & Use Cases

  • Node-based editor with Conversation, Tool, Condition, and Handoff nodes to model complex dialogues.
  • Deterministic flow control across steps with clear transition rules and state management.
  • Dashboards-friendly integration patterns for API calls, data passing, and error handling in real-world IVR and chat scenarios.

Quick Start

Open the Vapi Dashboard, create a new Workflow, and start adding nodes to map your conversation path.

Frequently Asked Questions about create-workflow

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

FAQPage Schema
How do I build deterministic conversational workflows with branching and tool calls?

Deterministic conversational workflows are built by visually composing node-based components like Conversation, Tool, Condition, and Handoff nodes to map multi-turn dialogue paths and enforce consistent transition rules.

When do I need node-based workflows for voice and chat conversations?

Node-based workflows are needed for multi-turn dialogue scenarios where branching, tool execution, and handoffs must be precisely managed to reduce prompt drift and runtime errors in IVR and chat applications.

How to manage conversation handoffs and state in Vapi?

Manage conversation handoffs and state in Vapi by using Handoff and Condition nodes within a visual workflow editor, applying deterministic flow control with clear transition rules across dialogue steps.

Can I integrate API calls and data passing into Vapi conversation flows?

Yes, API calls and data passing integrate into Vapi conversation flows using Tool nodes, which support dashboard-friendly patterns for executing API requests, passing data between steps, and handling errors.

Does create-workflow require a VAPI_API_KEY to function?

Yes, the create-workflow skill requires internet access and a valid VAPI_API_KEY to build and orchestrate deterministic conversations through the Vapi Dashboard integration.

What is the best way to prevent prompt drift in multi-step voice assistants?

Prevent prompt drift in multi-step voice assistants by replacing open-ended prompting with deterministic node-based workflows that enforce strict state management and transition rules across all dialogue branches.