Work with Voiceflow
For product questions and how-tos not answered by a relevant skill, follow the
documentation workflow: consult the docs MCP
before answering or implementing. This includes questions you encounter while
building or configuring. For every new Voiceflow troubleshooting issue, consult
the docs MCP even when a skill suggests the fix. Include the installed package,
active skill, and stage in why as described in that workflow. Reuse a retrieved
answer for the same issue. Public guidance does not require account setup.
For initial connection, read setup. After setup, ask what the user wants to build or improve before selecting any project.
For product work, read the operation contract, then only the specialist relevant to the task:
| Task | Skill |
|---|---|
| Build an agent or playbook | Build |
| Write global, routing, or playbook instructions | Prompting |
| Deterministic canvas logic | Workflows |
| Write function code | Functions |
| Connect inputs, outputs, and state | Wiring |
| Connect services, API tools, MCP, or secrets | Integrations |
| Import and query documents | Knowledge |
| Edit reusable messages and prompts | Messages |
| Configure spoken conversations | Voice |
| Install, customize, or troubleshoot a website widget | Widget |
| Diagnose behavior | Debug |
| Review customer conversations | Transcripts |
| Saved tests and quality checks | Evaluations |
| Drafts, environments, merging, publishing | Environments |
Product knowledge comes from the Voiceflow docs. Use the live CLI help or available MCP schemas for exact operation fields. Skills provide the workflow; they do not imply that every client exposes every operation. Say when a capability is unavailable rather than inventing a tool.
Skill metadata
--- name: voiceflow description: Answer Voiceflow product and how-to questions, or build, customize, deploy, inspect, and debug agents and website widgets. Routes tasks to focused skills and current documentation. license: MIT ---