Name: smsbump
Rating: 60.8 (1 reviews)
Author: membranedev

smsbump

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

Quality

71%

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/smsbump/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 a well-structured, actionable guide with concrete CLI commands, a clear connect-and-poll workflow with validation, and clean sectioning. Its main weaknesses are minor over-explanation, a slightly inconsistent step-numbering scheme, and the absence of any progressive split for the longer reference material.

Suggestions

Trim the overview paragraph and incidental prose ('This is the fastest way to get a connection') since Claude can infer their intent from the commands.

Fix the step numbering so 'Step 1' (connection ensure) is labelled consistently with the referenced 'Step 2' and the '1b' polling subsection.

Consider moving the proxy flag table and action-discovery details into a separate reference file so the main SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command blocks with brief context, but includes minor over-explanation such as the overview paragraph describing what SMSBump is and prose like 'This is the fastest way to get a connection' that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for the common cases — install, login (interactive and headless), connection ensure, polling, action list/run, and proxy requests — plus a concrete flag table, matching 'fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with validation via connection-state polling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (re-poll after the user acts), but the numbering is slightly inconsistent ('Step 2' is referenced with no labelled Step 1), matching the 'clear sequence with most checkpoints; minor validation gaps' anchor.	4 / 5
Progressive Disclosure	No bundle files exist, so the skill is a self-contained ~155-line body with clear section headers and only a one-level external docs link; structure is good and easy to navigate, but nothing is split into separate reference files, fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	17 / 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 pairs a what with an explicit 'Use when' trigger and is highly distinct thanks to the named product, but its capability wording is generic and its trigger terms lack natural SMS-marketing synonyms. Tightening the actions to SMSBump-specific tasks and broadening the trigger phrases would raise it.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with SMSBump-specific ones such as 'create and send SMS campaigns, automate SMS flows, and manage customers and orders'.

Broaden the trigger to natural user phrasing, e.g. 'Use when the user wants to send SMS campaigns, automate text message flows, or manage SMSBump data'.

Add file-format or entity keywords (campaigns, customers, orders) so the trigger matches more user requests.

Dimension	Reasoning	Score
Specificity	The description names the SMSBump domain but its actions — 'Manage data, records, and automate workflows' — are generic and not tied to SMSBump's actual capabilities (SMS campaigns, flows, customer support), fitting the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both a what ('SMSBump integration. Manage data, records, and automate workflows.') and an explicit when ('Use when the user wants to interact with SMSBump data.'), but the when clause is somewhat generic rather than concrete, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'SMSBump' is a natural product-name keyword and 'Use when the user wants to interact with SMSBump data' gives a trigger, but it misses common variations/synonyms a user would say such as 'SMS campaigns', 'text message marketing', or 'SMS flows'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product SMSBump in both the what and the when clause gives it a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.	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/smsbump/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.