Name: httpsms
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

httpsms

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

Quality

66%

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

Quality

Content

76%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 executable commands and a well-sequenced connection workflow including state validation. Its main weakness is the absence of verification steps for the destructive delete actions it lists, which caps workflow clarity.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive actions (e.g., 'Before running delete-* actions, confirm the target id with the user and verify it exists via the corresponding list action').

Fill the empty Description column in the Popular actions table or link each action to its schema details.

Verify the 'Official docs' link points to HttpSMS (it currently points to bulksms.com/developer), and trim the introductory HttpSMS marketing paragraph.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete commands and minimal padding, though the opening paragraph explaining what HttpSMS is ('for notifications, marketing, and two-factor authentication') and the 'Agent Types' line could be trimmed, matching the 'efficient; minor over-explanation' anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, connection get --wait, action list/run, request proxy) with --json flags and concrete parameter examples covering the common cases.	5 / 5
Workflow Clarity	The connect-and-poll sequence is well ordered with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the skill exposes destructive actions (delete-webhook, delete-message, delete-message-thread) with no validation or verification step before running them, which caps workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is organized into clear headed sections (Overview, Auth, Connecting, Searching, Popular actions, Proxy, Best practices); at ~150 lines some content like the actions table and proxy-flag table could be split out, leaving minor organization gaps rather than a fully ideal split.	4 / 5
	Total	16 / 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 has an explicit 'Use when' trigger and names the target product, but its capability list is generic template filler rather than concrete SMS actions. It is functional but indistinguishable from other Membrane integration descriptions.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete SMS actions like 'send and receive SMS messages, manage phone numbers, and configure webhooks'.

Add natural trigger terms users would actually say, such as 'SMS', 'text messages', or 'send texts'.

Tighten the 'when' clause to reference specific HttpSMS use cases (e.g., 'when the user wants to send or receive SMS via HttpSMS').

Dimension	Reasoning	Score
Specificity	Names the domain (HttpSMS) but the actions — 'Manage data, records, and automate workflows' — are generic and abstract rather than concrete SMS-specific operations, matching the 'names domain but actions minimal/generic' anchor.	2 / 5
Completeness	Both a 'what' clause ('Manage data, records, and automate workflows') and an explicit 'when' clause ('Use when the user wants to interact with HttpSMS data') are present; the 'what' is vague which keeps it below 5, but the explicit trigger keeps it above 3.	4 / 5
Trigger Term Quality	Contains the relevant product keyword 'HttpSMS' and an explicit trigger ('interact with HttpSMS data'), but misses natural synonyms users would say such as 'SMS', 'text messages', or 'send messages' that the body actually describes.	3 / 5
Distinctiveness Conflict Risk	The named product 'HttpSMS' gives it a clear niche with low conflict risk, but the generic 'data, records, workflows' phrasing reads like a template shared across Membrane integration skills, creating minor overlap risk.	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/httpsms/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.