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

textgain

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

Quality

Content

67%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 practical, command-driven guide with a clear connection lifecycle and feedback loops, scoring well on actionability and workflow clarity. It is held back by a padded intro and the absence of explicit post-action verification.

Suggestions

Trim the introductory paragraph about what Textgain is and the 'so you can focus on the integration logic' framing; Claude does not need the platform explained.

Add an explicit validation/verification step after running actions (e.g. inspect the `output` field for errors, or check `state` before relying on results) to close the workflow loop.

Show one fully-populated `membrane action list`/`action run` example with realistic values rather than only QUERY/CONNECTION_ID placeholders.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows (the intro 'Textgain is a text analytics platform that helps businesses understand customer feedback...' and 'so you can focus on the integration logic rather than auth plumbing'), fitting 'mostly efficient but includes some unnecessary explanation'; not a 4 because the padding is noticeable.	3 / 5
Actionability	Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request with a full flag table), matching 'mostly executable guidance; concrete commands with minor gaps'; not a 5 because some examples use placeholders (CONNECTION_ID, QUERY) without showing a fully populated case.	4 / 5
Workflow Clarity	Clear install -> login -> connection ensure -> wait-for-ready -> search -> run sequence with an explicit connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, matching 'clear sequence with most checkpoints present'; not a 5 because there is no explicit validation/verification step after running an action.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in a single well-sectioned SKILL.md with clear headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices), matching 'good structure; most content appropriately placed; minor organization gaps'; not a 5 because there is no overview-pointing-to-references pattern, though none is strictly required here.	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 well-formed with correct third-person voice, a 'Use when' trigger, and a clear Textgain niche, but its capability list is generic and the trigger lacks concrete user phrases or synonyms. It is solid but not exemplary.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Textgain capabilities, e.g. 'Run sentiment analysis, classify documents, and extract entities from text'.

Expand the 'Use when' clause with natural user phrases and synonyms, e.g. 'Use when the user wants to analyze text, run sentiment analysis, or classify Textgain documents'.

Add domain-specific terms (e.g. 'text analytics', 'sentiment', 'social-media reviews') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the Textgain domain plus a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it is not a 2 because more than one action is named, and not a 4 because the actions lack specificity.	3 / 5
Completeness	States both what ("Textgain integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Textgain data"), but the 'when' clause is generic rather than tied to concrete trigger phrases, matching the 'has both what and when; when could be more explicit' anchor; not a 5 because the trigger is not concrete.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Textgain", "data", "records", "workflows") and a 'Use when' trigger, but misses common variations, synonyms, or file/endpoint forms a user might say, fitting the 'some relevant keywords but missing common variations' anchor rather than the more complete 4.	3 / 5
Distinctiveness Conflict Risk	The Textgain brand and 'interact with Textgain data' trigger carve a clear niche with low overlap risk, though the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with adjacent data skills, matching 'mostly distinct; minor overlap risk'; not a 5 because the capability wording is not uniquely distinguishing.	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/textgain/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.