Name: burst-sms
Rating: 59.2 (1 reviews)
Author: membranedev

burst-sms

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

Quality

69%

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

Quality

Content

72%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 highly actionable with concrete, executable CLI commands and a clear connection state-machine flow, and it is reasonably concise. Its weaknesses are the absence of validation checkpoints around destructive/batch SMS actions and a monolithic structure with no reference-file split for the action and proxy catalogs.

Suggestions

Add a validation step before destructive/batch actions (e.g. confirm before cancel-sms, delete-from-list, remove-list, optout-list-member) and a verification step after send-sms using get-sms-delivery-status.

Move the full Popular actions table and the proxy flag reference into a references/ file (e.g. ACTIONS.md), keeping SKILL.md as a lean overview with a one-level-deep pointer.

Trim the opening product-description paragraph and remove the filler line "Use action names and parameters as needed." to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean CLI commands and a table with little padding, but the opening paragraph ("Burst SMS is a platform that allows businesses to send SMS messages...marketing, notifications, and alerts") and the filler line "Use action names and parameters as needed." could be trimmed. Not 5 due to these minor over-explanations; not 3 because commands are concrete and tight.	4 / 5
Actionability	Copy-pasteable `membrane` commands cover install, login (including headless completion), connection ensure/get with --wait, action list/run with --input, and proxy requests with a full flag table. Examples are executable and cover the common cases with real flags and JSON-output guidance.	5 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear and the connection state machine even has a re-poll feedback loop, but destructive/batch actions (cancel-sms, delete-from-list, remove-list, optout-list-member, send-sms to a list) have no validation or verification checkpoints. Per the rubric, missing validation for destructive/batch operations caps this dimension at 3.	3 / 5
Progressive Disclosure	The body is well-sectioned but is a single monolithic SKILL.md with no bundle files and no one-level-deep references, while the 17-row Popular actions table and the proxy flag table are inlined content that could live in a reference file. Not 4 because there are no separate-file references and a sizable action/flag catalog is inlined; not 2 because sectioning is solid.	3 / 5
	Total	15 / 20 Passed

Description

66%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 covers both what the skill does and when to use it, and its vendor-locked trigger makes it highly distinct. Its main weakness is generic, non-SMS-specific action language and limited natural trigger-term coverage.

Suggestions

Replace generic verbs with concrete Burst SMS actions, e.g. "Send SMS messages, manage contacts and contact lists, and check delivery status."

Add natural trigger phrases users would actually say, e.g. "Use when the user wants to send SMS, manage contacts or contact lists, or check SMS delivery and replies."

Mention key entities (SMS, contacts, lists, campaigns) so the description surfaces the domain's vocabulary rather than abstract "data" and "records."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Burst SMS domain plus a couple of action categories, but the actions are generic rather than concrete SMS-specific operations (no send SMS, contacts, lists, campaigns). It is not a 4 because the named actions are abstract, not "several specific actions."	3 / 5
Completeness	It states both a "what" ("Burst SMS integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Burst SMS data."). Not 5 because the "when" clause is generic rather than listing concrete trigger phrases; not 3 because both what and when are clearly present.	4 / 5
Trigger Term Quality	"Burst SMS," "data," "records," and "workflows" provide some relevant keywords, but common natural-phrase variations a user would say ("SMS," "text messages," "contacts," "send texts") are missing. Above 2 because the product name plus a few terms exceed one or two generic keywords; below 4 because coverage is not good.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named vendor product "Burst SMS" ("Use when the user wants to interact with Burst SMS data") gives a clear niche with minimal overlap risk against generic data skills. Matches the distinct-named-product anchor.	5 / 5
	Total	15 / 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/burst-sms/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.