Name: simpletexting
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

simpletexting

SimpleTexting integration. Manage Contacts, Campaigns, Keywords. Use when the user wants to interact with SimpleTexting data.

Quality

61%

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

Quality

Content

61%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, largely executable CLI guide with good state-handling on the connection flow. Its main weaknesses are a marketing-flavored intro that wastes tokens and the absence of validation checkpoints before destructive actions such as deleting campaigns or unsubscribing contacts.

Suggestions

Cut the marketing intro paragraph about what SimpleTexting is and who uses it; Claude does not need that context to use the CLI.

Add a validation checkpoint before destructive/batch actions — e.g. 'list-contacts' or 'get-campaign' to confirm the target, and user confirmation, before running delete-campaign/unsubscribe-contact/remove-contact.

Trim soft phrasing like 'so you can focus on the integration logic rather than auth plumbing' to factual command-oriented prose.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but the marketing intro ('businesses of all sizes looking to engage...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are explanation Claude does not need and could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request proxy) with real flags and JSON examples; minor gaps remain since action IDs are placeholders and parameter shapes come from the runtime schema rather than the doc.	4 / 5
Workflow Clarity	The connection sequence is well-ordered with state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but running destructive actions like 'Delete Campaign', 'Unsubscribe Contact', and 'Remove Contact from List' has no validation/confirmation checkpoint, capping this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the single self-contained SKILL.md is organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); the inlined 'Popular actions' table is small enough to stay inline, leaving only minor organization gaps.	4 / 5
	Total	14 / 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 is functional and clearly tied to a distinct named platform, with both a 'what' and 'when' clause present. It is held back by the generic verb 'Manage' and by trigger terms that omit the natural SMS/text-messaging phrasing a user would actually say.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Add, remove, and list contacts; create and send SMS/MMS campaigns; manage subscription keywords'.

Add natural trigger terms and synonyms users would say — 'SMS', 'text messages', 'text marketing', 'subscription keywords' — alongside 'SimpleTexting data'.

Tighten the 'when' clause to concrete triggers, e.g. 'Use when the user wants to send SMS/MMS campaigns, manage contacts or lists, or work with subscription keywords in SimpleTexting'.

Dimension	Reasoning	Score
Specificity	Names the domain (SimpleTexting) and three concrete entities ('Contacts, Campaigns, Keywords') but applies only the generic verb 'Manage' to all of them, so the actual actions are minimal rather than comprehensive.	3 / 5
Completeness	Both 'what' (SimpleTexting integration managing contacts/campaigns/keywords) and 'when' ('Use when the user wants to interact with SimpleTexting data') are explicit, though the 'when' clause is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes 'Contacts, Campaigns, Keywords' and 'SimpleTexting data' but misses the natural terms users actually say — 'SMS', 'text messages', 'text marketing', 'keywords' — so coverage lacks common synonyms.	3 / 5
Distinctiveness Conflict Risk	Naming a specific platform (SimpleTexting) gives a clear niche with minimal conflict risk, though the generic 'interact with...data' trigger leaves minor overlap with other SMS/messaging 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/simpletexting/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.