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

textline

Textline integration. Manage data, records, and automate workflows. Use when the user wants to interact with Textline 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/textline/SKILL.md

Quality

Content

63%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 executable CLI commands and a clear connection-state feedback loop, but its token efficiency is hurt badly by a duplicated, low-value entity list. Progressive disclosure is middling because everything is inlined.

Suggestions

Remove the duplicated routing entity list (the second half repeats the first); consider collapsing the full entity enumeration into a compact pointer to the official docs or a separate reference file.

Fix the dangling 'Step 2' reference by labeling the searching/running-actions section as Step 2, or rephrase to 'skip to Searching for actions'.

Tighten prose like 'This skill uses the Membrane CLI to interact with Textline' and the repeated 'discover before you build' guidance to remove restated content.

Dimension	Reasoning	Score
Conciseness	The body is padded by an ~90-item entity list whose second half is an exact duplicate of the routing entries, and several prose sections repeat guidance, fitting the 'noticeably verbose' anchor 2 rather than anchor 3.	2 / 5
Actionability	Every workflow step is backed by copy-paste-ready CLI commands (install, login, connection ensure/get, action list/run, request proxy) plus a flag table, matching the fully-executable anchor 5.	5 / 5
Workflow Clarity	There is a clear install→auth→connect→poll-state→search→run→proxy sequence with a polling feedback loop (BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the dangling 'Step 2' reference and unlabeled final step leave minor gaps at anchor 4.	4 / 5
Progressive Disclosure	Headers provide structure and no bundle files exist, but a large inlined entity list that could live in a separate reference and the absence of any one-level-deep detailed references place it at anchor 3.	3 / 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 third-person, names the domain, and includes an explicit 'Use when' trigger, so it clears the completeness bar. Weaknesses are generic action language and limited trigger-term variety.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Textline-specific actions (e.g., send/receive SMS, search conversations, manage contacts, pull reports).

Broaden trigger terms to natural phrasings users say, such as 'text a customer', 'send a bulk SMS', 'check a Textline conversation', or 'search Textline messages'.

Sharpen the 'when' clause to name concrete scenarios (e.g., 'Use when the user wants to send or read Textline messages, search contacts, or automate texting workflows').

Dimension	Reasoning	Score
Specificity	Names the Textline domain plus a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete, matching anchor 3 rather than the multi-specific-action anchor 4.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Textline data'), though the 'when' is somewhat generic, matching anchor 4.	4 / 5
Trigger Term Quality	Includes relevant terms ('Textline', 'data', 'records', 'workflows') but lacks common synonyms or natural user phrasings beyond the app name, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	The named Textline brand gives a clear niche with minimal conflict risk, though the generic action verbs leave minor overlap with other integration skills, fitting anchor 4.	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/textline/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.