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

textlocal

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

Quality

63%

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/textlocal/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 content is highly actionable with copy-paste Membrane CLI commands and a useful actions table, and it is reasonably well-structured. Its main weaknesses are a padded conceptual intro and an absence of validation/verification checkpoints for destructive and batch messaging operations.

Suggestions

Add explicit validation/verification steps before destructive or batch actions, e.g. confirm the recipient list and message body before 'send-sms', and verify delivery status afterwards.

Trim the introductory background ('Think of it as an API to programmatically send texts') since Claude already understands SMS/messaging platforms; lead directly with the integration workflow.

Consider moving the full popular-actions and proxy-flag tables into a references file and keeping only the most common examples inline to improve token efficiency and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples and tables, but the intro ('Think of it as an API to programmatically send texts') and background on what Textlocal is explain concepts Claude already knows and could be trimmed.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connect, action discovery, action run with JSON input, and proxy requests, plus a concrete popular-actions table covering the common cases.	5 / 5
Workflow Clarity	The install→login→connect→run sequence is clear, but the skill exposes destructive and batch operations (send-sms to contact groups, delete-contact, cancel-scheduled) with no validation or verification checkpoints, which caps workflow clarity at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	It is a single well-organized file with clear section headers and no nested references, with only minor bulk content (the actions and proxy-flag tables) inlined; structure is good though it slightly leans on inline reference material.	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 includes an explicit 'Use when' trigger and leverages a distinctive brand name, but its capability list is generic rather than concrete and it omits the natural SMS/messaging trigger terms users would say. It is competent but could be sharpened with specific actions and synonyms.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Textlocal capabilities such as 'send SMS, manage contacts and groups, schedule and cancel messages'.

Add natural user trigger phrases and synonyms, e.g. 'Use when the user wants to send SMS or text messages, manage contacts, or check message history via Textlocal'.

Tighten the 'when' clause to reference the actual use cases (marketing campaigns, alerts, contact management) rather than the circular 'interact with Textlocal data'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Textlocal) but the actions 'Manage data, records, and automate workflows' are minimal and generic verb+noun pairs rather than concrete capabilities like sending SMS or managing contacts.	2 / 5
Completeness	It provides an explicit 'Use when the user wants to interact with Textlocal data' trigger and a 'what' statement, so both are present; the 'what' is vague and the 'when' could be more specific, matching the 'both present but could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Textlocal' is repeated as a genuine product keyword and 'interact with Textlocal data' is a usable phrase, but it lacks the natural SMS-specific variations users would actually say such as 'send SMS', 'text messages', or 'campaigns'.	3 / 5
Distinctiveness Conflict Risk	The named brand 'Textlocal' establishes a clear niche with low conflict risk, though the generic 'interact with Textlocal data' trigger leaves minor overlap with other messaging/CRM skills.	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/textlocal/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.