Name: smsapi
Rating: 62.4 (1 reviews)
Author: membranedev

smsapi

SMSAPI integration. Manage SMSes, Contacts, Groups, Campaigns, Templates. Use when the user wants to interact with SMSAPI data.

Quality

73%

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

Quality

Content

68%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.

A highly actionable integration guide with copy-paste commands and good connection-state handling, but it is padded with an unnecessary platform intro and lacks validation checkpoints for the batch/destructive SMS operations it ultimately drives.

Suggestions

Trim the opening platform-description paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' — Claude already knows what SMS is.

Add a validation/checkpoint step around running actions (e.g., confirm recipients and message content with the user before sending SMS/campaigns, and verify the response `output` for errors), since sending SMS is a costly, irreversible batch operation.

Fix the broken 'skip to Step 2' cross-reference by labeling the workflow steps (Step 1: connect, Step 2: search/run actions) or rewording to a concrete heading link, and de-duplicate the 'Searching for actions' and 'Popular actions' sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command blocks, but the opening paragraph explaining what SMS/SMSAPI is and its use cases, plus filler like 'so you can focus on the integration logic rather than auth plumbing', are unnecessary explanations Claude does not need — anchor 3 ('mostly efficient but includes some unnecessary explanation').	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases end to end (install, login, connection ensure, polling, action list/run, proxy request) plus a complete flag table — a clean match for anchor 5.	5 / 5
Workflow Clarity	The connection setup has good feedback loops (poll → state → client action → re-poll), but 'skip to Step 2' references a step that is never labeled, and running SMS/campaign actions is a batch/destructive operation with no validation checkpoint before or after — per the rubric, missing validation in batch operations caps this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md is appropriately self-contained with clear, logically ordered section headers; only minor redundancy between 'Searching for actions' and 'Popular actions' keeps it at anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

78%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.

A solid, third-person description that names a specific platform and lists concrete managed entities with an explicit 'Use when' trigger. Its main weakness is a generic trigger phrase and a single collapsed verb, which keep specificity and completeness just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists five concrete entities ('Manage SMSes, Contacts, Groups, Campaigns, Templates') giving comprehensive domain coverage, but collapses them under a single generic verb rather than distinct concrete action verbs, so it lands at anchor 4 ('several specific actions; minor gaps') rather than 5.	4 / 5
Completeness	Both 'what' (manage the listed entities) and 'when' ('Use when the user wants to interact with SMSAPI data') are explicitly present, but the 'when' is circular and lacks concrete trigger phrases, fitting anchor 4 ('when could be more explicit or specific') rather than 5.	4 / 5
Trigger Term Quality	Good keyword coverage (SMSes, Contacts, Groups, Campaigns, Templates, SMSAPI), but it misses natural synonyms users might say (e.g. 'text messages', 'bulk SMS') and the trigger phrase 'interact with SMSAPI data' is generic, matching anchor 4 ('good coverage; a few natural terms missing') rather than 5 (which requires synonyms/extensions).	4 / 5
Distinctiveness Conflict Risk	'SMSAPI' is a named brand that anchors a clear niche, and the trigger references it explicitly, giving minimal conflict risk with other skills — a clean match for anchor 5.	5 / 5
	Total	17 / 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/smsapi/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.