Name: snatchbot
Rating: 52.8 (1 reviews)
Author: membranedev

snatchbot

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

Quality

58%

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

Quality

Content

60%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 delivers strong executable CLI guidance and a well-sequenced connection workflow with validation checkpoints, but it is dragged down by a large padded noun list that adds no actionable value. Tightening that list and validating action/proxy results would lift the weakest dimensions.

Suggestions

Replace the ~47-item noun bullet list with a short sentence on available resource types, or move it to a reference file, to cut padding.

Add a validation/verification step after 'action run' and 'request' (e.g. check the output/error field before proceeding) to strengthen workflow_clarity.

Normalize the step numbering (the 'Step 2' reference has no labeled Step 1/2) so the connection sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The ~47-item bullet list of bare nouns (Bot, Interaction, Channel, ... App Store, Marketplace) with no actions or purpose is padded filler, matching the 'noticeably verbose; several padded sections' anchor.	2 / 5
Actionability	Concrete executable commands are given throughout (npm install, membrane login, connection ensure, action list/run, request) plus a proxy flag table; placeholders like CONNECTION_ID and QUERY need substitution, leaving a minor gap below anchor 5.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state checkpoints and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the later action-running and proxy sections lack result validation and step numbering is inconsistent, fitting anchor 4.	4 / 5
Progressive Disclosure	With no bundle files present, the body is organized into clear logical sections with headers; minor gaps (the inline noun list and inconsistent step labels) keep it just below anchor 5.	4 / 5
	Total	14 / 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 is clear and includes an explicit 'Use when' trigger tied to a distinct named app, but its capability verbs are generic and it lacks keyword variations. It is functional but could be sharpened with concrete operations and richer trigger phrasing.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete SnatchBot operations such as 'create bots, send broadcasts, manage contacts and channels'.

Add natural trigger synonyms users might say, e.g. 'Use when the user mentions SnatchBot, chatbots, bot broadcasts, or wants to automate messaging workflows'.

Tie the 'when' clause to specific intents (e.g. querying bot analytics, triggering flows) rather than the broad 'interact with SnatchBot data'.

Dimension	Reasoning	Score
Specificity	Phrases like 'Manage data, records, and automate workflows' name the SnatchBot domain but use generic verbs ('manage', 'automate') rather than concrete operations, matching the 'minimal or generic actions' anchor.	2 / 5
Completeness	It states a 'what' (SnatchBot integration, manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with SnatchBot data'); the trigger is present but the 'what' is generic, so it sits at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with SnatchBot data' surfaces the brand keyword but offers limited coverage and no synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named app 'SnatchBot' gives a clear niche with minimal conflict risk, though generic 'manage data' actions leave minor overlap with related data skills.	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/snatchbot/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.