Name: botconversa
Rating: 53.6 (1 reviews)
Author: membranedev

botconversa

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

Quality

60%

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

Quality

Content

57%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 action-oriented with strong concrete CLI commands and a reasonable connection workflow, but it is bloated by a valueless actions table and an unnecessary intro, lacks validation steps for destructive operations, and does not split any detail into reference files.

Suggestions

Add a validation/verification checkpoint before destructive actions (e.g. 'Before delete-subscriber, fetch and confirm the subscriber with get-subscriber-by-phone') to satisfy the destructive-operations workflow cap.

Move the 20-row 'Popular actions' table (all 'No description') into a references/actions.md file, or replace 'No description' with one-line summaries, to cut token bloat.

Trim the introductory paragraph explaining what BotConversa is — Claude can infer this — and lead directly with the CLI workflow.

Extract the proxy request flag reference table into a references/proxy.md file, keeping only a one-line example inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the introductory paragraph explaining what BotConversa is and the 20-row 'Popular actions' table where every description reads 'No description' are padding that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (membrane login, connection ensure, action list/run, request) with real flag examples; minor gaps remain around resolving action IDs and parameter schemas.	4 / 5
Workflow Clarity	The connect-to-run flow is sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive and batch operations (e.g. 'Delete Subscriber', bulk list actions) have no validation or verification steps, which caps this at 3 per the rubric.	3 / 5
Progressive Disclosure	The skill has clear section headers but is a single ~175-line monolithic file with no bundle files; the actions table and proxy flag reference are inlined content that could live in separate reference files.	3 / 5
	Total	13 / 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 adequate: it names the product, gives a few actions, and includes an explicit 'Use when' trigger. It is held back by generic action verbs and missing entity-level trigger terms (subscribers, campaigns, flows).

Suggestions

Replace generic verbs ('Manage data, records') with concrete BotConversa operations such as 'manage subscribers, campaigns, flows, and tags' to lift specificity.

Expand the 'Use when' clause to list entity-level triggers, e.g. 'Use when the user wants to manage BotConversa subscribers, campaigns, flows, or send messages.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('BotConversa integration') and lists a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete API-level operations, so coverage is not comprehensive.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with BotConversa data') are present; the 'when' is explicit but somewhat narrow, so it is not a perfect 5.	4 / 5
Trigger Term Quality	It includes the natural product name 'BotConversa' and a 'Use when the user wants to interact with BotConversa data' trigger, but misses common entity-level synonyms (subscribers, campaigns, flows, messages) that users would actually say.	3 / 5
Distinctiveness Conflict Risk	The named product 'BotConversa' gives it a clear niche with low conflict risk, but the generic action verbs ('manage data, records') leave minor overlap risk with other CRM/messaging skills.	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/botconversa/SKILL.md
Commit: f484c82

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