Name: botmaker
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

botmaker

Botmaker integration. Manage Organizations. Use when the user wants to interact with Botmaker 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/botmaker/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 highly actionable with concrete CLI commands and a clear connection state machine, but it is held back by a padded intro, a wasted empty-description actions table, inconsistent step numbering, and no use of bundle files for the reference-style content. Tightening prose and splitting out the action/flag tables would improve it.

Suggestions

Trim the opening marketing paragraph to one line and fill or remove the empty Description column in the Popular actions table to improve conciseness.

Fix the step numbering so '1b' and the 'Step 2' reference map to clearly labeled steps, and add an explicit 'verify state is READY before proceeding' checkpoint to reach full workflow clarity.

Move the Popular actions and proxy flag reference tables into a referenced file (e.g., references/actions.md) and link to it from the body to apply progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening marketing-style paragraph ('a platform for building and managing chatbots... used by companies looking to improve customer engagement') and the Popular actions table with empty Description columns add padding; it fits the anchor for mostly efficient with some unnecessary explanation, not the lean 4.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (npm install, membrane login, membrane connection ensure, membrane action run, membrane request) with flag explanations and JSON-output guidance, matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The install → auth → connect → poll-until-ready → search → run sequence is clear with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, matching the anchor for a clear sequence with most checkpoints present; it is not 5 because step numbering is inconsistent (a '1b' and a 'Step 2' reference with no matching labels).	4 / 5
Progressive Disclosure	No bundle files exist and everything is inlined in a ~165-line SKILL.md with no one-level-deep references (only an external docs URL); the Popular actions and proxy-options tables are reference-style content that could live in separate files, fitting the anchor for some structure with content that should be separate left inline; it is not 4 because no file split is signaled despite the non-trivial length.	3 / 5
	Total	15 / 20 Passed

Description

66%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 cleanly states a what and a when tied to a distinct named platform, but it is thin on concrete actions (only 'Manage Organizations') and trigger synonyms. Expanding the action list and trigger phrasing would lift specificity and trigger quality.

Suggestions

Replace the single 'Manage Organizations' action with several concrete actions the skill actually supports (e.g., send messages, create catalogs, get session metrics) to raise specificity.

Add natural trigger terms and synonyms users would say (e.g., 'Botmaker chatbots', 'Botmaker campaigns', 'send a Botmaker message') rather than only 'interact with Botmaker data'.

Make the 'when' clause more concrete by listing the specific use cases that should activate the skill.

Dimension	Reasoning	Score
Specificity	The description names the Botmaker domain and one concrete action ('Manage Organizations'), matching the anchor for naming a domain with 1-2 concrete actions that are not comprehensive; it does not list the many other actions visible in the body (Send Message, Create Catalog, etc.), so it is not a 4.	3 / 5
Completeness	Both 'what' (Botmaker integration, Manage Organizations) and 'when' (Use when the user wants to interact with Botmaker data) are explicitly present, matching the anchor where both exist but 'when' could be more specific; it is not 5 because the trigger phrasing is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes a 'Use when the user wants to interact with Botmaker data' trigger and the natural keyword 'Botmaker', but offers few synonyms or variations, fitting the anchor for some relevant keywords missing common variations; it is above 2 (which has only generic keywords) but lacks the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Naming a specific platform ('Botmaker integration') with a distinct trigger ('interact with Botmaker data') gives a clear niche with minimal conflict risk against other skills, matching the top anchor.	5 / 5
	Total	15 / 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/botmaker/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.