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

sms-everyone

SMS Everyone integration. Manage Users, Groups, Contacts, Lists, Campaigns, Templates. Use when the user wants to interact with SMS Everyone data.

Quality

68%

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

Quality

Content

75%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 highly actionable with executable CLI commands and a clear connection state-machine workflow, but it carries some padding (an introductory analogy and an inlined LLM apology) that hurts token efficiency. Structure is clean for a single-file skill.

Suggestions

Remove the inlined apology line ('I am sorry, I cannot provide an API or developer documentation URL...') and the 'Think of it as email marketing' analogy to tighten the intro.

Fix the dangling 'skip to Step 2' reference by adding a matching 'Step 2' header or relabeling it to point at the 'Searching for actions' section.

Reconcile the inconsistent action-list invocations ('membrane action list' vs 'npx @membranehq/cli@latest action list') to a single canonical form.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command documentation, but the introductory analogy ('Think of it as email marketing, but for text messages') and the inlined LLM apology ('I am sorry, I cannot provide an API or developer documentation URL...') are unnecessary padding that could be trimmed.	3 / 5
Actionability	Provides copy-paste ready CLI commands throughout (install, login, connection ensure, action list/run, request proxy) with a flag table, covering the common cases with executable, complete syntax.	5 / 5
Workflow Clarity	Clear install→authenticate→connect→discover→run sequence with a state-machine polling loop and explicit handling of READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states, though the 'skip to Step 2' reference dangles without a matching header.	4 / 5
Progressive Disclosure	No bundle files exist; the single self-contained file is organized into clear, well-signaled sections appropriate for a CLI usage doc, with only minor content (the proxy flag table, detailed state machine) that could optionally be split out.	4 / 5
	Total	16 / 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 answers both what and when with an explicit trigger clause, but its action vocabulary is generic and it skips the core SMS-sending capability. Trigger terms lean on the product name and entity list rather than natural user phrasing.

Suggestions

Replace the single generic verb 'Manage' with distinct concrete actions (e.g., 'Send SMS campaigns, manage contacts, groups, lists, and templates').

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

Make the 'Use when' clause more specific, e.g., 'Use when the user wants to send or schedule SMS campaigns, or manage SMS Everyone contacts and groups.'

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates several managed entities ('Users, Groups, Contacts, Lists, Campaigns, Templates'), but relies on a single generic verb ('Manage') and omits the platform's core SMS-sending action, leaving coverage incomplete.	3 / 5
Completeness	Provides a clear 'what' ('Manage Users, Groups, Contacts, Lists, Campaigns, Templates') and an explicit 'Use when the user wants to interact with SMS Everyone data' trigger, though the 'when' is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the product name and entity terms, but misses the natural phrases users would actually say such as 'send SMS', 'text messages', or 'bulk SMS', so common variations are absent.	3 / 5
Distinctiveness Conflict Risk	The named product 'SMS Everyone' carves a clear niche with minimal conflict risk, though the generic CRM-style entity vocabulary (Users, Groups, Contacts, Campaigns) could overlap with related marketing skills.	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-everyone/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.