Name: ottertext
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ottertext

OtterText integration. Manage Recordses. Use when the user wants to interact with OtterText 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/ottertext/SKILL.md

Quality

Content

81%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 and workflow-clear, with executable commands and an explicit connection-state feedback loop. The only real weakness is mild verbosity in the opening marketing description and some content that could be split into a reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening marketing prose ("OtterText is an SMS marketing platform. It allows businesses to send text messages...") and audience explanation are background Claude could infer, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Fully executable copy-paste commands cover the common cases (install, login, connection ensure, action list/run, proxy) plus a complete proxy-flag reference table, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The install → login → connect → poll-state → search → run sequence has an explicit readiness state machine (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a poll-again feedback loop, matching the 'clear sequence with explicit validation steps and feedback loops' anchor.	5 / 5
Progressive Disclosure	No bundle files exist and content is organized under clear headers (Overview, Working with OtterText, Popular actions, Best practices), but the inlined proxy-flag table and detailed state machine could live in a reference file, fitting 'good structure; minor organization gaps' rather than a clean 5.	4 / 5
	Total	17 / 20 Passed

Description

50%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 names a specific integration, but the capability description is thin ('Manage Recordses') and the trigger language is generic. Specificity and trigger-term quality are the weakest dimensions.

Suggestions

Replace the vague 'Manage Recordses' with concrete actions the skill performs (e.g., 'Send SMS campaigns, manage contacts, retrieve message history').

Expand the 'Use when...' clause with natural user phrases such as 'sending SMS marketing messages', 'OtterText contacts', or 'SMS campaign analytics'.

Fix the non-word 'Recordses' to a clear capability verb/object.

Dimension	Reasoning	Score
Specificity	The description names the domain ("OtterText integration") and one generic action ("Manage Recordses") but provides no comprehensive set of concrete actions, matching the 'names domain but actions minimal/generic' anchor rather than the 1-2 concrete actions required for a 3.	2 / 5
Completeness	Both 'what' ("OtterText integration. Manage Recordses.") and an explicit 'when' ("Use when the user wants to interact with OtterText data.") are present, matching the anchor where both exist but the 'when' could be more specific; not a 3 because the trigger clause is explicit, not a 5 because the 'what' is thin and 'when' is generic.	4 / 5
Trigger Term Quality	Only the generic phrase "interact with OtterText data" appears, with no natural synonyms or variations a user would actually say, fitting the 'one or two generic keywords; missing natural phrases' anchor.	2 / 5
Distinctiveness Conflict Risk	"OtterText" names a specific niche with low broad conflict risk, fitting 'mostly distinct; minor overlap risk'; not a 5 because the trigger phrasing is generic rather than concrete user-mention terms.	4 / 5
	Total	12 / 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/ottertext/SKILL.md
Commit: f484c82

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