Name: landbot
Rating: 60 (1 reviews)
Author: membranedev

landbot

Landbot integration. Manage Leads, Persons, Organizations, Deals, Pipelines, Activities and more. Use when the user wants to interact with Landbot data.

Quality

70%

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

Quality

Content

61%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 well-structured and highly actionable with concrete CLI commands and a useful actions table, but it is slightly verbose in the intro/overview and lacks validation guidance for the destructive actions it lists. The connection workflow itself is sequenced well with explicit state checkpoints.

Suggestions

Trim the opening marketing paragraph ("no-code chatbot builder... marketing, sales, and customer support teams") and the vague "Use action names and parameters as needed" line — Claude does not need Landbot's market positioning.

Add a verification/confirmation step before destructive action runs (e.g., "Before delete-customer or block-customer, confirm the customer ID with the user and consider list-customers first"), which would lift workflow clarity past the destructive-operation cap.

Add one fully-worked end-to-end example with real values (e.g., list customers → get a customer → update it) to close the actionability gap to a 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening "Landbot is a no-code chatbot builder... used by marketing, sales, and customer support teams" and the vague "Landbot Overview" tree followed by "Use action names and parameters as needed" are unnecessary padding that could be trimmed.	3 / 5
Actionability	It provides concrete executable commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run") plus a real actions table, but examples rely on placeholders like <actionId> and /path/to/endpoint with no fully-worked end-to-end example, leaving minor gaps below a 5.	4 / 5
Workflow Clarity	The connection flow has a clear state-based sequence with poll/retry checkpoints (BUILDING, READY, CLIENT_ACTION_REQUIRED), but the popular-actions table includes destructive operations (delete-customer, block-customer, archive-customer) with no verification step before running them, which caps workflow clarity at 3 per the rubric's destructive-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist and the single file is well-organized with clear section headers (Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy), though the 16-row Popular actions table arguably belongs in a separate reference file, leaving minor organization gaps below a 5.	4 / 5
	Total	14 / 20 Passed

Description

78%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 names the domain and provides an explicit "Use when..." trigger, scoring well on completeness and distinctiveness. Its weakness is that the enumerated entities (Leads, Persons, Organizations, Deals, Pipelines, Activities) do not match the skill body, which actually covers customers, bots, webhooks, channels, and WhatsApp templates — a misleading capability list.

Suggestions

Replace the generic "Manage Leads, Persons, Organizations, Deals, Pipelines, Activities" list with the entities the skill actually exposes (customers, bots, channels, webhooks, WhatsApp templates) so the description reflects real capabilities.

Use distinct action verbs instead of one generic "Manage" (e.g., "Create, list, update, and delete customers; send WhatsApp template messages; manage webhooks").

Add concrete trigger variations to the "when" clause (e.g., "Use when the user wants to manage Landbot customers, send WhatsApp messages, or configure bots").

Dimension	Reasoning	Score
Specificity	"Manage Leads, Persons, Organizations, Deals, Pipelines, Activities and more" enumerates several concrete entities, though the single generic verb "Manage" means distinct actions are not each named, keeping it below a 5.	4 / 5
Completeness	Both "what" ("Landbot integration. Manage Leads, Persons...") and "when" ("Use when the user wants to interact with Landbot data") are present and explicit, but the trigger clause is a single broad phrase rather than multiple concrete triggers, which the 5 anchor requires.	4 / 5
Trigger Term Quality	The phrase "Use when the user wants to interact with Landbot data" supplies the natural trigger ("Landbot" / "Landbot data") repeated across the description, but coverage is thin with no synonyms since Landbot has no file-extension variants, so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	"Landbot integration" tied to the named app "Landbot" is a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/landbot/SKILL.md
Commit: f484c82

Reviewed: 6 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.