Name: sailthru
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

sailthru

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sailthru/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 solid, actionable integration guide with concrete Membrane CLI commands and a well-sequenced, state-aware connection workflow. It loses points mainly to a padded marketing intro, some redundant sections, and the absence of any progressive-disclosure file split for the denser reference material.

Suggestions

Remove or trim the opening marketing paragraph ('Sailthru is a marketing automation platform...') since it restates background Claude can infer.

Merge the redundant 'Searching for actions' and 'Popular actions' sections into a single action-discovery block to avoid repeating the `action list` command.

Move the detailed connection-state handling and the proxy flags table into a separate reference file, leaving SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening marketing paragraph ('Sailthru is a marketing automation platform for retailers and publishers...') explains concepts Claude need not be told, and the 'Searching for actions' and 'Popular actions' sections redundantly repeat the action-list command.	3 / 5
Actionability	Provides copy-paste ready commands for install, login, connection ensure, action run, and proxy requests, plus a flags table — mostly executable with minor gaps such as abstract placeholders in the proxy examples.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop after user action; the downstream task-execution workflow is looser ('search then run').	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers with no nested or buried references, but at ~140 lines with detailed connection-state handling inlined and no external reference files, it is not the lean simple-skill case that would score 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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 functional: it states the domain, lists a few actions, and includes an explicit 'Use when' trigger tied to the Sailthru brand, making it clearly distinct. Its main weakness is generic action language and a thin set of natural trigger terms.

Suggestions

Replace generic actions with concrete ones, e.g. 'Manage users, lists, blasts, and templates' to match the skill's actual capabilities.

Broaden the trigger clause with natural synonyms, e.g. 'Use when the user wants to send email blasts, manage subscriber lists, or work with Sailthru campaigns.'

Drop redundant phrasing between 'Sailthru integration' and the action list to tighten the description.

Dimension	Reasoning	Score
Specificity	Names the Sailthru domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete — it omits the specific entities the body reveals (User, List, Blast, Template).	3 / 5
Completeness	Explicitly answers both what ('Sailthru integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Sailthru data.'), but the 'when' is generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	Contains the brand name and one trigger phrase ('interact with Sailthru data') but lacks common synonyms users would say, such as email campaigns, blasts, lists, or marketing automation.	3 / 5
Distinctiveness Conflict Risk	Sailthru is a named product giving the skill a clear niche with distinct, brand-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/sailthru/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.