Name: mobile-text-alerts
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mobile-text-alerts

Mobile Text Alerts integration. Manage Accounts. Use when the user wants to interact with Mobile Text Alerts 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/mobile-text-alerts/SKILL.md

Quality

Content

68%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 copy-paste CLI commands and a clear connection-to-execution workflow, but it pads product background and lacks validation/verification steps for batch messaging operations. Structure is clean but monolithic.

Suggestions

Add a verification/feedback step after running actions, e.g. polling connection state or confirming a sent-message result before declaring success, to satisfy the batch-operations validation requirement.

Trim the opening paragraph defining what Mobile Text Alerts is, assuming Claude can infer the platform's purpose from context, to improve token efficiency.

Consider moving the clientAction state breakdown and the proxy flag table into a separate reference file so SKILL.md stays a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening platform-definition paragraph ('Mobile Text Alerts is a platform that allows businesses...used for marketing, notifications, alerts, and reminders') pads product context that could be trimmed, matching the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands for install, login, connection ensure, polling, action list/run with JSON input, and proxy requests with a complete flag table, covering the common cases.	5 / 5
Workflow Clarity	A clear install-login-connect-search-run sequence with state-based polling checkpoints exists, but the skill performs batch/messaging operations with no validation or verification steps after running actions, so the destructive/batch cap applies and prevents scoring above 3.	3 / 5
Progressive Disclosure	Single-file content is well-sectioned and navigable with no nested references, but some inline detail like the clientAction breakdown and proxy flag table could be split into a reference file, keeping it just below a 5.	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 is clear and explicit about both purpose and trigger, anchored to a distinct platform, but is thin on concrete capabilities and natural trigger synonyms like 'SMS' or 'text messages'. It sits solidly in the upper-middle range.

Suggestions

Replace generic 'Manage Accounts' with concrete actions users perform, e.g. 'send SMS campaigns, manage subscriber lists, and trigger keyword-based alerts'.

Add natural trigger phrases such as 'SMS', 'text messages', 'alerts', and 'notifications' so the description matches how users actually phrase the request.

Tighten the 'Use when' clause to specific scenarios, e.g. 'Use when the user wants to send or schedule SMS/text alerts via Mobile Text Alerts.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Mobile Text Alerts integration') and one concrete action ('Manage Accounts'), matching the 1-2 concrete actions anchor without reaching the 'several specific actions' of a 4.	3 / 5
Completeness	Provides both a clear 'what' and an explicit 'when' ('Use when the user wants to interact with Mobile Text Alerts data'), but the trigger is generic so it does not reach the concrete-trigger-phrases bar of a 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Mobile Text Alerts', 'Accounts', 'interact with...data') but omits natural user phrases like SMS, text messages, alerts, or notifications, so it is not a 4.	3 / 5
Distinctiveness Conflict Risk	Names a specific niche platform with distinct triggers and only minor overlap risk from the generic 'data' framing, placing it just below the minimal-conflict 5.	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/mobile-text-alerts/SKILL.md
Commit: f484c82

Reviewed: 6 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.