Name: instabot
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

instabot

Instabot integration. Manage Chatbots, Users. Use when the user wants to interact with Instabot data.

Quality

75%

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

Quality

Content

88%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 and well-sequenced, with executable commands, a decision-tree for connection states, and feedback loops for polling. Its only notable weakness is mild verbosity in the framing prose and a large inline actions table that could be split into a reference file.

Suggestions

Trim the marketing overview paragraph about what Instabot is and the "rather than auth plumbing" aside; assume Claude knows the domain context.

Move the 20-row "Popular actions" table into a references file (e.g. ACTIONS.md) and keep only 3-5 high-value examples inline, linking to the rest.

Consider extracting the connection-state decision tree into a short reference so the main flow stays lean while edge-case handling remains one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, built around executable CLI commands and a compact actions table. It includes a few unnecessary asides (the marketing overview of what Instabot is, and "so you can focus on the integration logic rather than auth plumbing") that could be trimmed, matching the score-4 anchor of efficient with minor over-explanation. It does not reach 5 because those padding passages remain.	4 / 5
Actionability	It provides copy-paste-ready commands with concrete flags and --json examples, plus parameter passing and a proxy-request reference table that cover the common cases, matching the score-5 anchor. There are no pseudocode gaps that would drop it to 4.	5 / 5
Workflow Clarity	The connect-to-run flow is clearly sequenced with explicit state-based decision branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), a polling loop, and a feedback loop (poll again after the user completes the action). This matches the score-5 anchor of clear sequence with explicit validation and error-recovery feedback.	5 / 5
Progressive Disclosure	Content is organized into clear sections with no nested references and no bundle files present, so navigation is straightforward. It stays at 4 rather than 5 because the long inline "Popular actions" table is content that could live in a separate one-level-deep reference file, leaving a minor organization gap.	4 / 5
	Total	18 / 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 successfully answers both what the skill does and when to use it, and the explicit platform name keeps conflict risk low. Its main weakness is generic action phrasing ("Manage") and limited trigger-term coverage, which hold back specificity and trigger quality.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List and start chats, send transcripts, assign chats to admins, generate reports".

Broaden trigger terms to natural user phrasing such as "Instabot chatbots, conversations, live chat, message templates" rather than only "Chatbots, Users, Instabot data".

Keep the explicit "Use when..." clause but make the trigger more concrete, e.g. "Use when the user wants to work with Instabot chatbots, conversations, or live chat data."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Instabot integration") and entities ("Chatbots, Users") but the only action verb is the generic "Manage", which is minimal/generic rather than concrete like list/extract/start. It sits below the score-3 anchor because no specific concrete actions are enumerated, and above score-1 because the domain and objects are clearly named.	2 / 5
Completeness	Both "what" ("Instabot integration. Manage Chatbots, Users") and "when" ("Use when the user wants to interact with Instabot data") are present, satisfying the score-4 anchor where the 'when' could be more explicit or specific. It does not reach 5 because the trigger phrase is generic ("interact with Instabot data") rather than concrete multi-trigger phrasing.	4 / 5
Trigger Term Quality	It includes some relevant natural keywords ("Chatbots", "Users", "Instabot data") but misses common variations and synonyms a user might say (e.g., "conversations", "bot workflows", "live chat"). This matches the anchor for some relevant keywords with missing variations, rather than score 4 which would require broader natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform "Instabot" gives it a clear niche with distinct triggers and minimal conflict risk with other skills, matching the score-5 anchor. No neighboring anchor fits better since the platform name sharply scopes it.	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/instabot/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.