Name: sms-partner
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

sms-partner

SMS Partner integration. Manage Accounts. Use when the user wants to interact with SMS Partner data.

Quality

65%

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

Quality

Content

67%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 integration guide built almost entirely from executable Membrane commands, with a clear connection workflow and state-driven feedback. Its main weaknesses are occasional marketing-style padding and a 'Popular actions' section that stays generic rather than naming SMS Partner-specific actions.

Suggestions

Trim conversational padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection'.

Populate 'Popular actions' with concrete SMS Partner examples (e.g. send a campaign, fetch delivery status, list conversations) rather than only restating the discovery command.

Resolve the dangling 'Step 2' reference by labeling the target section, and add a brief note to verify action output before reporting success to the user.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and short prose, but several lines are padded (e.g. 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') that could be trimmed without losing information.	3 / 5
Actionability	Concrete executable commands are given throughout (install, login, connection ensure, action run, proxy flags table), with only a minor gap: the 'Popular actions' section is generic and lists no SMS Partner-specific actions.	4 / 5
Workflow Clarity	There is a clear connect -> search -> run sequence with a state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop; minor gaps are the unlabeled 'Step 2' reference and the absence of any output validation step.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections and is reasonably sized and self-contained, with no nested or buried references; it stops short of 5 because no content is split into one-level-deep reference files.	4 / 5
	Total	15 / 20 Passed

Description

62%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 establishes a clear niche and includes both a 'what' and an explicit 'Use when' clause, but it is thin on concrete capabilities and on the natural trigger phrases a user would actually say. Strengthening the action list and trigger synonyms would raise it from solid to strong.

Suggestions

Add the concrete actions the skill supports (e.g. 'send SMS campaigns, transactional alerts, and bulk messages') instead of the single phrase 'Manage Accounts'.

Expand the 'Use when' clause with natural user phrasings such as 'send an SMS', 'SMS marketing campaign', 'bulk text messages', or 'transactional SMS alerts'.

Replace the generic 'interact with SMS Partner data' with specific trigger contexts to reduce overlap with a general messaging skill.

Dimension	Reasoning	Score
Specificity	Names the domain ('SMS Partner integration') and one concrete action ('Manage Accounts'), matching the anchor for a domain plus 1-2 concrete actions; it does not list several actions, so it stays below 4.	3 / 5
Completeness	Both a 'what' ('SMS Partner integration. Manage Accounts.') and an explicit 'when' ('Use when the user wants to interact with SMS Partner data.') are present, but the trigger is generic rather than concrete phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	It includes the natural product term 'SMS Partner' and 'Accounts', but misses common variations a user would actually say such as 'send SMS', 'SMS marketing', 'bulk text', or 'transactional alerts'.	3 / 5
Distinctiveness Conflict Risk	The product name 'SMS Partner' gives it a clear, distinct niche with minimal conflict risk, though the generic 'interact with SMS Partner data' trigger leaves minor overlap with a general SMS/messaging skill.	4 / 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/sms-partner/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.