Name: typebot
Rating: 58.4 (1 reviews)
Author: membranedev

typebot

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

Quality

68%

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

Quality

Content

78%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 executable commands and a well-sequenced connection-readiness workflow including a polling feedback loop. Its main weaknesses are the absence of progressive disclosure (no referenced bundle files, reference material inlined) and a missing validation checkpoint for action results.

Suggestions

Move the proxy flag reference table and the detailed clientAction state schema into separate reference files (e.g., REFERENCE.md) and link to them from SKILL.md to improve progressive disclosure.

Add an explicit validation step after running actions (check the output field, handle errors, retry on failure) to close the workflow validation gap for potentially destructive operations.

Trim the introductory "Typebot is a no-code chatbot builder..." paragraph since it explains background Claude largely already knows, tightening conciseness toward the lean anchor.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete commands and brief explanations, with only minor instances of over-explanation such as the introductory "Typebot is a no-code chatbot builder" sentence, matching the efficient anchor with minor trim opportunities.	4 / 5
Actionability	The content provides fully executable, copy-paste-ready commands (npm install, membrane login, connection ensure, action run) plus a complete flag table, covering the common cases with specific examples, matching the highest anchor.	5 / 5
Workflow Clarity	There is a clear sequence (install, auth, connect, poll, search, run) with an explicit polling feedback loop for connection readiness, but result-handling after running actions lacks a validate/retry checkpoint, matching the clear-sequence anchor with minor validation gaps.	4 / 5
Progressive Disclosure	The body has clear section structure but no bundle files exist and no external references are used, while content that could live in separate files (the proxy flag reference table, the detailed clientAction schema) is inlined, matching the some-structure anchor with inline content that should be separate.	3 / 5
	Total	16 / 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 successfully pairs a named-domain "what" with an explicit "Use when" trigger, but its action verbs are generic ("manage data, records, automate workflows") rather than concrete Typebot-specific capabilities. Tightening the verbs to specific operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Typebot actions (e.g., "create and manage chatbots, read submission results, and update workspace variables") to improve specificity.

Add natural trigger synonyms users would actually say, such as "chatbot," "conversational form," or "Typebot submission/results," to broaden trigger-term coverage.

Make the "when" clause more explicit by listing concrete triggers (e.g., "Use when the user mentions Typebot, chatbot submissions, or wants to read/modify Typebot results").

Dimension	Reasoning	Score
Specificity	The description names the domain (Typebot) but the actions "Manage data, records, and automate workflows" are minimal and generic rather than concrete, matching the anchor that names the domain with generic actions rather than the level above which lists specific concrete actions.	2 / 5
Completeness	Both the "what" (Typebot integration managing data, records, workflows) and the "when" (Use when the user wants to interact with Typebot data) are present, though the "when" clause could be more specific, matching the anchor that has both with a slightly less explicit when.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Typebot data" provides the domain keyword and a trigger clause, but lacks natural synonyms or variations users would commonly say, matching the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app "Typebot" establishes a clear niche with minimal conflict risk, though the generic verb phrases ("manage data, records") create minor overlap risk with other data-integration skills, keeping it just below the fully-distinct anchor.	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/typebot/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.