Tessl • The management layer for AI agent skills

SkillPublic

buildchatbot

BuildChatbot integration. Manage data, records, and automate workflows. Use when the user wants to interact with BuildChatbot 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/buildchatbot/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 body delivers a largely actionable, copy-paste-ready CLI workflow with explicit connection-state handling, but it is undermined by broken step references ('Step 2' never defined), some marketing padding, and a redundant Popular actions section. As a single-file skill it is reasonably well structured.

Suggestions

Fix the broken workflow numbering: the text references 'Step 2' twice but no Step 1/Step 2 headings exist — renumber the workflow (Install → Authenticate → Connect → Poll until READY → Discover actions → Run actions) explicitly.

Cut the marketing sentence about 'businesses of all sizes' and merge the 'Popular actions' section into 'Searching for actions' to remove the duplicated command.

Add one fully worked end-to-end example (a real --intent query, a chosen action, and a run command with an --input payload) and verify the 'Official docs' link, which currently points to an IBM Watson Assistant URL rather than BuildChatbot.

Dimension	Reasoning	Score
Conciseness	Commands are given directly and tersely, but the body includes marketing fluff ('used by businesses of all sizes to automate customer service, lead generation, and internal communications'), filler ('so you can focus on the integration logic rather than auth plumbing'), and a 'Popular actions' section that duplicates the earlier search command. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than anchor 4, where only minor trimming would be needed.	3 / 5
Actionability	Concrete executable CLI commands throughout (npm install, membrane login, connection ensure, connection get --wait, action list/run, request with a full flag table) with only placeholder gaps. Not a 5 because there is no fully worked example with a real intent, actionId, or input payload showing a complete call.	4 / 5
Workflow Clarity	The sequence (install, authenticate, connect, poll to READY, search actions, run) exists with explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the text says 'skip to Step 2' twice while no Step 1 or Step 2 headings exist, and the steps are scattered across sections. This fits 'steps listed but validation gaps; sequence present but checkpoints missing or implicit' territory rather than anchor 4's coherent numbered flow.	3 / 5
Progressive Disclosure	The ~140-line body is self-contained (no bundle files exist) and well organized into clear sections with concrete examples inline. It fits 'good structure; most content is appropriately placed; minor organization gaps' — the proxy flag table and duplicated 'Popular actions' section could be consolidated or moved to a reference file.	4 / 5
	Total	14 / 20 Passed

Description

50%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 pairs a capability statement with an explicit 'Use when' clause and anchors on a distinctive platform name, but its action list is generic filler. Specific natural trigger terms (chatbot, dataset, flow) are largely absent.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions, e.g. 'Create and update chatbot datasets, run flows, and manage records in BuildChatbot'.

Add natural trigger terms users would actually say, such as 'chatbot', 'bot', 'dataset', or 'flow', alongside the platform name.

Make the 'when' clause more specific, e.g. 'Use when the user mentions BuildChatbot or wants to manage chatbot datasets, flows, or records'.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the BuildChatbot domain but the actions are generic with no concrete operations (e.g. no 'create datasets', 'run flows', 'deploy chatbots'). It matches 'Names the domain but actions are minimal or generic' rather than anchor 3, which requires 1-2 concrete actions.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' trigger ('Use when the user wants to interact with BuildChatbot data') are present. It is not a 5 because the 'what' is vague and the 'when' is a single broad clause without concrete trigger phrases.	4 / 5
Trigger Term Quality	The only distinctive keyword is 'BuildChatbot'; 'data', 'records', and 'workflows' are generic. Natural user phrases like 'chatbot', 'bot', 'dataset', or 'flow' are missing, matching 'One or two generic keywords; missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	The named platform 'BuildChatbot' gives a clear niche trigger, but the generic 'manage data, records, and automate workflows' phrasing creates minor overlap risk with general data/automation skills, fitting 'Mostly distinct; minor overlap risk'.	4 / 5
	Total	12 / 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/buildchatbot/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

buildchatbot

Table of Contents

Is this your skill?