Name: textmagic
Rating: 55.2 (1 reviews)
Author: membranedev

textmagic

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

Quality

62%

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/textmagic/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 a well-structured, largely executable guide to driving TextMagic through the Membrane CLI, with a clear connection workflow and validation checkpoints. It loses points mainly to mild over-explanation and an undefined "Step 2" reference.

Suggestions

Define "Step 2" — the text says "skip to Step 2" but no Step 2 heading exists; rename or add the target section.

Trim tutorial-style padding ("Think of it as an API for sending SMS messages", "so you can focus on the integration logic rather than auth plumbing") that assumes Claude lacks basic context.

Consider moving the full resource-type list and proxy flag table into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but pads with explanations Claude doesn't need — "Think of it as an API for sending SMS messages" and "so you can focus on the integration logic rather than auth plumbing". Not a 4 because several sentences restate concepts Claude already knows; not a 2 because the bulk is actionable commands rather than sustained verbosity.	3 / 5
Actionability	Provides concrete, executable `membrane` commands throughout (login, connection ensure, action list/run, request) with a flag table and JSON examples. Not a 5 because placeholders like CONNECTION_ID and a few implied steps leave minor gaps; not a 3 because the guidance is genuinely executable, not pseudocode.	4 / 5
Workflow Clarity	Clear sequence (install → authenticate → connect → poll state → search actions → run) with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a feedback loop (poll again after the user completes an action). Not a 5 because the "Step 2" target is never defined and some transitions are implicit; not a 3 because validation checkpoints and a retry loop are present.	4 / 5
Progressive Disclosure	No bundle files exist; the skill is a self-contained, well-sectioned single document (Overview, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references. Not a 5 because the long inline resource list and full flag table could live in a separate reference file; not a 3 because structure is clear and nothing is buried or nested.	4 / 5
	Total	15 / 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 correctly identifies the TextMagic niche and includes both a what and a when clause, but its action language is generic and it omits the natural SMS/messaging trigger terms users would actually say.

Suggestions

Replace generic verbs with concrete TextMagic actions, e.g. "Send and receive SMS messages, manage contacts and lists, schedule messages".

Add natural trigger terms users would say — "SMS", "text messages", "messaging" — to the Use-when clause.

Tighten the when clause to concrete triggers, e.g. "Use when the user wants to send SMS, manage TextMagic contacts, or check message status."

Dimension	Reasoning	Score
Specificity	Names the TextMagic domain but its actions — "Manage data, records, and automate workflows" — are generic and abstract rather than concrete (no mention of sending SMS, managing contacts, or lists). Not a 3 because it lacks 1-2 genuinely concrete actions; not a 1 because the domain is named and multiple (if vague) actions are listed.	2 / 5
Completeness	States both a "what" ("Manage data, records, and automate workflows") and a "when" ("Use when the user wants to interact with TextMagic data"). Not a 5 because the "when" is generic and lacks concrete trigger phrases; not a 3 because both what and when are explicitly present.	4 / 5
Trigger Term Quality	Includes the relevant keyword "TextMagic" and "data", but misses the natural terms users would actually say — "SMS", "text messages", "messaging". Not a 4 because common variations/synonyms are absent; not a 2 because there is at least one genuinely relevant keyword tied to the named service.	3 / 5
Distinctiveness Conflict Risk	Naming a specific service ("TextMagic integration") gives it a clear niche with minimal conflict risk against unrelated skills. Not a 5 because the generic action language ("Manage data, records") could overlap with other integration/data skills; not a 3 because the TextMagic name makes it mostly distinct.	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/textmagic/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.