Name: herobot-chatbot-marketing
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

herobot-chatbot-marketing

HeroBot Chatbot Marketing integration. Manage Organizations. Use when the user wants to interact with HeroBot Chatbot Marketing data.

Quality

64%

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/herobot-chatbot-marketing/SKILL.md

Quality

Content

67%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 a strong, actionable integration guide with concrete CLI commands and a well-sequenced connection state machine. Its main weaknesses are a padded product-introduction paragraph and the absence of any progressive-disclosure reference files.

Suggestions

Trim the opening HeroBot product-description paragraph and soft filler sentences to assume Claude's competence and save tokens.

Add one fully-worked end-to-end example that chains `action list` -> taking an `id` -> `action run` with a concrete `--input` and reading the `output` field.

Consider moving the popular-actions and proxy-flag reference tables into a separate reference file referenced from SKILL.md to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI commands and tables, but opens with a product-marketing paragraph about what HeroBot is and includes soft sentences ('so you can focus on the integration logic rather than auth plumbing') that Claude does not need.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands across install, auth, connect, search, run, and proxy, with documented flags and a popular-actions table; minor gap is that no single end-to-end worked example ties the placeholders (CONNECTION_ID, <actionId>) together.	4 / 5
Workflow Clarity	The connection flow is a clear state-machine sequence (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a poll-again feedback loop, but the 'skip to Step 2' reference is loosely labeled and there is no validation step after running an action.	4 / 5
Progressive Disclosure	Well-organized into logical sections with clear navigation and appropriately inlined content for a focused integration guide; the minor gap is that no bundle/reference files exist and reference-style tables (popular actions, proxy flags) live entirely in SKILL.md.	4 / 5
	Total	15 / 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 correctly identifies a distinct product niche and includes an explicit 'Use when' trigger, but it is thin on concrete capabilities, naming only one (misaligned) action. Expanding the action list would materially improve it.

Suggestions

Replace 'Manage Organizations' with the skill's primary concrete actions (e.g., send messages, create users, manage campaigns and leads) to better reflect actual scope.

Add natural trigger phrases users would say, such as 'chatbot campaigns', 'leads', or 'send a HeroBot message', beyond the product name.

Tighten the 'when' clause to name the specific data the user wants to work with rather than the generic 'interact with data'.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Manage Organizations'), but the action is minimal and misaligned with the skill's actual scope, and 'interact with HeroBot Chatbot Marketing data' is generic.	2 / 5
Completeness	Has an explicit 'Use when the user wants to interact with HeroBot Chatbot Marketing data' clause and a 'what' statement, but the 'what' is thin and the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the product name and 'chatbot marketing' as natural triggers, but misses common variations and synonyms (campaigns, leads, messages, users) a user might say.	3 / 5
Distinctiveness Conflict Risk	Names a specific product (HeroBot Chatbot Marketing), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	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/herobot-chatbot-marketing/SKILL.md
Commit: f484c82

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