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

Blog Docs Log in Get started

botpress

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/botpress/SKILL.md

Quality

Content

76%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 commands and reference tables, and is reasonably concise and well-structured. Its main weakness is workflow clarity: destructive and batch operations lack validation checkpoints, and the connection workflow references an undefined 'Step 2'.

Suggestions

Add explicit validation/confirmation guidance before destructive and batch actions (e.g. verify a conversation ID before delete-conversation, or confirm row count before create-table-rows).

Fix the undefined 'Step 2' reference by either numbering the overall workflow (Connect -> Search -> Run) or removing the dangling 'skip to Step 2' language.

Trim the introductory 'Botpress is an open-source conversational AI platform...' paragraph and the proxy preamble to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, but includes a few over-explanatory passages (the opening 'Botpress is an open-source...' paragraph and some introductory prose) that could be trimmed. Matches anchor 4 rather than 5.	4 / 5
Actionability	It provides copy-paste-ready membrane commands (login, connection ensure, action list/run, request) plus a full actions table and proxy flag table covering the common cases. Fully executable guidance matching anchor 5.	5 / 5
Workflow Clarity	The connection flow has state checks and a poll-again feedback loop, but the overall steps are not coherently numbered ('Step 2' is referenced but never defined), and the destructive/batch actions (delete-user, delete-conversation, create-table-rows) lack validation checkpoints. Per the rubric, missing validation in destructive/batch operations caps this at 3.	3 / 5
Progressive Disclosure	No bundle files exist; content is a single file with clear section headers and good organization, though the 20-row action table and proxy flag table are inlined as bulk reference material rather than split out. Sits at anchor 4 with minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

61%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 establishes a clear, distinct niche (Botpress) with an explicit 'Use when' clause, but its capability statement is generic ('Manage Bots') and the trigger phrasing is thin. It is solid on distinctiveness and completeness but weak on specificity.

Suggestions

Replace 'Manage Bots' with concrete actions, e.g. 'Manage Botpress bots, users, conversations, messages, and tables.'

Expand the 'Use when' clause with more natural trigger phrases, e.g. 'Use when the user wants to list or create Botpress users, conversations, messages, or manage bot data.'

Add a couple of natural synonyms users might say (e.g. 'chatbot', 'Botpress bot') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the Botpress domain ('Manage Bots') but the actions are minimal and generic with no concrete operations listed. It falls below anchor 3, which requires 1-2 specific named actions.	2 / 5
Completeness	Both 'what' ('Botpress integration. Manage Bots.') and an explicit 'when' ('Use when the user wants to interact with Botpress data.') are present, though the trigger clause is somewhat generic. Fits anchor 4 rather than 5, which requires concrete multi-case trigger phrases.	4 / 5
Trigger Term Quality	It includes relevant natural keywords ('Botpress', 'Bots', 'Botpress data') that users would say, but lacks common variations or synonyms beyond the product name. Matches anchor 3 ('some relevant keywords but missing common variations').	3 / 5
Distinctiveness Conflict Risk	Botpress is a specific named product with a clear niche and distinct trigger ('interact with Botpress data'), giving minimal conflict risk with other skills. Matches anchor 5.	5 / 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/botpress/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.