Name: voiceflow
Rating: 55.2 (1 reviews)
Author: membranedev

voiceflow

Voiceflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Voiceflow data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/voiceflow/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, actionable integration guide with executable Membrane CLI commands and a clear connection state-machine workflow. It loses points for some unnecessary preamble and slightly inconsistent step numbering, but is broadly strong.

Suggestions

Trim the opening overview paragraph describing who uses Voiceflow; Claude does not need the market positioning to run the commands.

Fix step numbering so the flow reads as a clean 1-2-3 sequence instead of jumping to '1b' and referencing an unlabelled 'Step 2'.

Move the proxy flags table and best-practices list into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary explanation such as the opening paragraph on who uses Voiceflow and phrases like 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (login, connection ensure, action list/run, request) with flag tables, but a few placeholders (CONNECTION_ID) and an unexplained 'Step 2' reference leave minor gaps.	4 / 5
Workflow Clarity	The connect-then-poll-then-act sequence is clear with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though step numbering is inconsistent ('1b', referenced 'Step 2').	4 / 5
Progressive Disclosure	Well-organized into clear sections with no bundle files present; all content is inline but appropriately sectioned, with only minor gaps where reference material (e.g. the proxy options table) could live separately.	4 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies the Voiceflow niche and includes an explicit 'Use when' trigger, but its action list is generic ('manage data, records, automate workflows') rather than concrete. Tightening the capabilities to specific Voiceflow operations would raise specificity and trigger quality.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Voiceflow operations, e.g. 'manage projects, prototypes, traces, and user workspaces'.

Add natural trigger synonyms users might say, such as 'Voiceflow projects', 'Voiceflow conversations', or 'chatbot/voice assistant design'.

Make the 'when' clause more specific by naming the entities users work with (projects, traces, workspaces) rather than 'Voiceflow data' generically.

Dimension	Reasoning	Score
Specificity	Names the Voiceflow domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete Voiceflow-specific operations.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Voiceflow data') are present, though the 'when' could be more specific.	4 / 5
Trigger Term Quality	The keyword 'Voiceflow' is repeated but the description lacks natural synonyms or variations a user might say beyond 'interact with Voiceflow data'.	3 / 5
Distinctiveness Conflict Risk	The Voiceflow brand gives it a clear niche with a distinct trigger, with only minor overlap risk against generic data-integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/voiceflow/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.