Name: typeform
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

typeform

Typeform integration. Manage Forms, Workspaces. Use when the user wants to interact with Typeform data.

Quality

71%

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/typeform/SKILL.md

Quality

Content

68%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 content is highly actionable with concrete Membrane CLI commands throughout and a solid connection-state workflow, but it is padded with an unnecessary Typeform explainer and lacks validation safeguards around its destructive delete actions.

Suggestions

Remove the opening paragraph explaining what Typeform is and the filler line "When to use which actions: Use action names and parameters as needed." — Claude already knows this and they consume context.

Add a validation/confirmation step before destructive actions, e.g. require listing the target form and confirming with the user before running delete-form or delete-responses, to lift workflow clarity above the destructive-operations cap.

Consider moving the 20-row Popular-actions table into a references file (e.g. references/actions.md) referenced from the body, to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but opens with a three-sentence explainer of what Typeform is and who uses it ("Typeform is an online form and survey creation tool..."), plus filler like "When to use which actions: Use action names and parameters as needed.", which is unnecessary explanation Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request proxy) with concrete flags and a comprehensive Popular-actions table plus an options table, covering the common cases fully.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with state-based polling checkpoints (READY/CLIENT_ACTION_REQUIRED/ERROR), but the skill exposes destructive actions (delete-form, delete-responses) with no validation or confirmation workflow before them, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Single-file skill (no references/scripts/assets bundle) organized into clear headed sections (Overview, Working with Typeform, Popular actions, Proxy, Best practices); structure is good, though the 20-row Popular-actions table is bulk content that could live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

73%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 is well-formed with an explicit Use-when trigger and a distinct Typeform niche, but it is held back by the generic verb "Manage" which understates the concrete actions the skill actually supports.

Suggestions

Replace the generic verb "Manage" with the concrete actions the skill supports, e.g. "List, create, update, and delete Forms and Workspaces, and retrieve form Responses."

Add common trigger synonyms to the Use-when clause such as "surveys" and "responses" so it fires on natural user phrasing.

Dimension	Reasoning	Score
Specificity	"Manage Forms, Workspaces" names the Typeform domain and two concrete entities, but the verb "Manage" is generic rather than enumerating concrete actions (list/create/update/delete), placing it between the minimal-actions anchor (2) and the 1-2-concrete-actions anchor (3).	3 / 5
Completeness	Both halves are present — the "what" ("Manage Forms, Workspaces") and an explicit "when" ("Use when the user wants to interact with Typeform data"), but the "what" is generic and the trigger phrase lacks concrete enumerated scenarios, so it is not the fully-explicit anchor 5.	4 / 5
Trigger Term Quality	Includes natural terms "Typeform", "Forms", "Workspaces" plus an explicit "Use when..." trigger, but omits common variations a user might say such as "responses" and "surveys", matching the good-coverage-with-a-few-missing-terms anchor.	4 / 5
Distinctiveness Conflict Risk	"Typeform integration" names a specific branded application, giving it a clear niche with distinct triggers and minimal conflict risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	16 / 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/typeform/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.