Name: chatbot-builder
Rating: 55.2 (1 reviews)
Author: membranedev

chatbot-builder

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

Quality

63%

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/chatbot-builder/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 body is highly actionable, with concrete CLI commands and a clear connection-state workflow including feedback loops. It loses points on intro verbosity and, more importantly, on missing validation guidance for destructive and batch action execution.

Suggestions

Add a validation/confirmation step before destructive actions — e.g. 'Before delete-* actions, confirm the target id with the user or read it back via get-* first' — to satisfy the destructive-operations workflow cap.

Trim the opening marketing paragraph ('Chatbot Builder is a platform that allows users to create and deploy chatbots without coding...') to a one-line context statement.

Consider moving the 'Popular actions' table into a references/ file referenced from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The CLI command reference is efficient, but the opening platform description ('create and deploy chatbots without coding... used by marketers, customer support teams') and rationale prose explain context Claude does not need and could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover every common case (install, login, connection ensure, action list/run, request proxy) and a flag-options table makes parameters concrete and executable.	5 / 5
Workflow Clarity	The connection state machine is well sequenced with explicit polling/feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive operations (delete opportunity, delete tag) and batch sends get a bare 'membrane action run' with no validation or confirmation checkpoint, capping the score per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The single file is well sectioned with clear headers and no nested references; the main gap is the 20-row 'Popular actions' table, which could optionally live in a separate reference file rather than inline.	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 correctly uses third-person voice and includes an explicit 'Use when' trigger tied to a named product, answering both what and when. Its main weakness is generic, non-concrete action language and thin trigger-term variation.

Suggestions

Replace generic verbs with concrete Chatbot Builder capabilities, e.g. 'Create and send flows, manage contacts, tags, and opportunities, and trigger automated conversation sequences.'

Expand the 'Use when' clause with concrete user phrases such as 'when the user mentions chatbots, flows, contacts, or opportunities in Chatbot Builder'.

Add task-level synonyms (flows, contacts, pipelines, opportunities, tags) so the description surfaces for a wider range of natural requests.

Dimension	Reasoning	Score
Specificity	The domain (Chatbot Builder) is named, but the listed actions — 'Manage data, records, and automate workflows' — are generic abstractions that could describe almost any data tool rather than concrete capabilities.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Chatbot Builder data') are present and explicit, though the when clause could cite more concrete trigger phrases.	4 / 5
Trigger Term Quality	'Chatbot Builder' is a natural user term and 'interact with Chatbot Builder data' is a usable trigger, but coverage relies on a single product name with no synonyms or task-level variations users would naturally say.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named 'Chatbot Builder' product gives it a distinct niche with minimal conflict risk, though the generic 'manage data/records' phrasing leaves minor overlap with other data-management 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/chatbot-builder/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.