Name: sms-magic
Rating: 61.6 (1 reviews)
Author: membranedev

sms-magic

SMS Magic integration. Manage SMSes, Contacts, Conversations, Templates, Campaigns, Lists. Use when the user wants to interact with SMS Magic 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/sms-magic/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 content is concrete and actionable with a solid sequenced workflow and good feedback loops for connection setup. Its weaknesses are over-explanation in the intro, inconsistent step numbering, and missing validation guidance for batch/destructive campaign operations.

Suggestions

Trim the intro paragraph that explains SMS Magic's business purpose and CRM integrations, and remove guidance duplicated between 'Searching for actions' and 'Popular actions' to improve conciseness.

Fix the step numbering: label the section referenced as 'Step 2' and renumber '1b' (currently there is no '1'), or replace the numbered cross-references with descriptive links.

Add a validation/verification checkpoint for batch or destructive operations such as sending campaigns (e.g., confirm recipient count or preview before a bulk send), since the current workflow only validates the connection setup.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the intro paragraph over-explains SMS Magic's business purpose and the "Best practices" section restates earlier guidance, matching anchor 3 (mostly efficient with some unnecessary explanation) rather than the minor-trim anchor 4.	3 / 5
Actionability	Copy-paste-ready commands cover the common workflow (install, login incl. headless, connection ensure/get --wait, action list/run with JSON input, proxy flags table), matching anchor 4; it stops short of 5 because the proxy section lacks a combined concrete example.	4 / 5
Workflow Clarity	There is a clear install→auth→connect→search→run sequence with real feedback loops in the connect flow (poll --wait, state-based branching, re-poll after CLIENT_ACTION_REQUIRED), fitting anchor 4; inconsistent step numbering ("skip to Step 2"/"1b" with no matching labels) and absent send-side validation keep it from 5.	4 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear section headers and no nested references matches anchor 4; with no external file split, some redundancy ("Popular actions" vs "Searching for actions"), and over 50 lines, it does not reach the well-signaled one-level-deep references of anchor 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.

The description clearly states what the skill does and when to use it, with strong distinctiveness from a named platform. Its main weakness is a generic "when" clause and limited verb/action variety that keep specificity and trigger quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	"Manage SMSes, Contacts, Conversations, Templates, Campaigns, Lists" names several specific actions across six entity types, matching anchor 4; it falls short of 5 because a single repeated verb ("Manage") lacks the varied concrete actions of the top anchor.	4 / 5
Completeness	It has both an explicit "what" ("Manage SMSes, Contacts…Lists") and an explicit "when" ("Use when the user wants to interact with SMS Magic data"), so it clears the cap-at-3 rule; the single generic "when" clause keeps it at 4 rather than the multi-trigger anchor 5.	4 / 5
Trigger Term Quality	"SMS Magic", "SMSes", and the entity names (Contacts, Campaigns, Lists) give good natural keyword coverage, but synonyms like "texts"/"texting"/"send SMS" are missing, fitting anchor 4 rather than the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	"SMS Magic integration" ties the skill to a specific named platform with distinct triggers, giving it a clear niche and minimal conflict risk, matching 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/sms-magic/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.