Name: botpenguin
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

botpenguin

BotPenguin integration. Manage Chatbots. Use when the user wants to interact with BotPenguin data.

Quality

70%

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

Quality

Content

82%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 is highly actionable with concrete CLI commands and a well-sequenced, validated connection workflow, supported by clean section organization. Minor gains are available from trimming the marketing-style intro and adding an output-validation note for run actions.

Dimension	Reasoning	Score
Conciseness	Quotes like "membrane connection ensure \"https://botpenguin.com/\" --json" and the compact best-practices bullets are efficient and assume competence; only the opening "BotPenguin is a platform that lets businesses build chatbots..." intro leans slightly over-explained and could be trimmed.	4 / 5
Actionability	Quotes provide copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run with --input JSON, request proxy flags) plus a populated Popular actions table, fully covering the common cases with executable guidance.	5 / 5
Workflow Clarity	Quotes sequence the connection flow with explicit checkpoints (ensure -> poll --wait until not BUILDING -> handle CLIENT_ACTION_REQUIRED -> READY -> search -> run) including a retry-after-action feedback loop, but the action-running half lacks an explicit output validation step, leaving minor gaps below the 5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and content is organized under clear section headers; structure is good but the Popular actions and proxy-options tables are inlined in a single file with no one-level-deep references, sitting just below the well-split 5 anchor.	4 / 5
	Total	17 / 20 Passed

Description

57%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 answers both what and when and anchors on a distinct proper noun, but its capability phrasing is generic and trigger coverage is narrow. Tightening the action list and adding synonyms would raise specificity and trigger quality.

Suggestions

Replace the generic "Manage Chatbots" with concrete actions (e.g., 'list chats, update leads, import contacts, send WhatsApp messages') to lift specificity.

Add natural trigger synonyms and the product's file/extension cues (e.g., 'chatbots, BotPenguin chats, WhatsApp templates, lead inbox') to broaden trigger coverage.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage BotPenguin chats, leads, contacts, or WhatsApp messaging.'

Dimension	Reasoning	Score
Specificity	Quotes "BotPenguin integration. Manage Chatbots." name the domain but the single action "Manage Chatbots" is generic and minimal, matching the anchor that names the domain with minimal/generic actions rather than the 1-2 concrete-action anchor.	2 / 5
Completeness	Quotes provide both a 'what' ("Manage Chatbots") and an explicit 'when' ("Use when the user wants to interact with BotPenguin data"), but the 'what' is thin and the 'when' could be more specific, matching the both-present-but-could-be-tighter anchor.	4 / 5
Trigger Term Quality	Quotes "BotPenguin" and "Chatbots" surface the key proper-noun trigger and one synonym, but common variations are missing and "Chatbots" is generic, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The proper noun "BotPenguin" carves a clear niche with minimal conflict risk, but the generic term "Chatbots" creates minor overlap with other chatbot-related skills, fitting the mostly-distinct anchor.	4 / 5
	Total	13 / 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/botpenguin/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.