Name: chatbotkit
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

chatbotkit

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

Quality

66%

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

Quality

Content

71%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 a well-structured, actionable integration guide with concrete CLI commands and a sound connection-readiness feedback loop. Its main weaknesses are mild verbosity in the intro, a missing end-to-end worked example, and no progressive disclosure into reference files despite bulky inline tables.

Suggestions

Move the Popular actions table and the proxy flag reference into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Trim the opening platform-description paragraph to a single line, since it restates context Claude can infer from the integration name.

Add one end-to-end worked example that takes a returned connection id and feeds it into `membrane action run` so the full flow is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with copy-paste commands, but the opening 'ChatBotKit is a platform for building and deploying AI chatbots...' paragraph and the large 18-row Popular actions table are mild over-explanation that could be trimmed, keeping it just below a 5.	4 / 5
Actionability	It provides concrete, executable commands with flags (login, connection ensure, action run, request) and a proxy fallback, but lacks an end-to-end worked example substituting a returned connection id into a subsequent action call, leaving a minor gap.	4 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear with a real feedback loop (polling BUILDING state and branching on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but a few checkpoints are implicit, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	Section headers give reasonable structure, but for a >50-line skill the bulky inline Popular actions table and proxy-flag table are content that belongs in a separate reference file, and no external references are signaled at all.	3 / 5
	Total	15 / 20 Passed

Description

62%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 adequately specific and correctly pairs a 'what' with an explicit 'Use when' clause in third-person voice, but its action verbs and trigger terms are generic and lack synonyms. It is solid but not exemplary.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete ChatBotKit actions such as 'list and create conversations, messages, contacts, datasets, and bots'.

Add natural trigger synonyms users might say (e.g. 'chatbots, conversations, ChatBotKit records') beyond the single platform name.

Make the 'Use when' clause more concrete by naming the specific entities (conversations, datasets, bots) rather than the abstract phrase 'interact with ChatBotKit data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('ChatBotKit integration') and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete — it does not reach the 'several specific actions' bar of a 4.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with ChatBotKit data') are present, but the trigger is somewhat generic rather than the concrete trigger phrases required for a 5.	4 / 5
Trigger Term Quality	It relies on the single keyword 'ChatBotKit' (repeated in the 'Use when' clause) but offers no natural synonyms or variations a user might say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying everything to the named platform 'ChatBotKit' gives it a clear, mostly distinct niche with minimal conflict risk, though the generic 'data/records' actions leave minor overlap risk versus a 5.	4 / 5
	Total	14 / 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/chatbotkit/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.