Name: sendlane
Rating: 61.6 (1 reviews)
Author: membranedev

sendlane

Sendlane integration. Manage Persons, Organizations, Lists, Tags, Broadcasts, Automations and more. Use when the user wants to interact with Sendlane data.

Quality

73%

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/sendlane/SKILL.md

Quality

Content

75%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.

A highly actionable skill body built around concrete, executable Membrane CLI commands with a clear connection-state workflow. The main drag is a padded marketing intro and minor redundancy, plus a dangling "Step 2" reference.

Suggestions

Delete the opening marketing paragraph ("Sendlane is an email marketing automation platform...") — it explains the product rather than instructing Claude.

Fix the "Step 2" references by labeling the Searching/Running-actions section as Step 2, or reword to "skip to Searching for actions".

De-duplicate the action-list command (it appears under both "Searching for actions" and "Popular actions").

Dimension	Reasoning	Score
Conciseness	The opening marketing paragraph ("Sendlane is an email marketing automation platform... drive sales") and the redundant restatement of the action-list command in "Popular actions" are unnecessary padding, landing it at mostly-efficient-with-some-trimmable explanation rather than lean.	3 / 5
Actionability	It provides copy-paste-ready, executable commands throughout (membrane login, connection ensure, action list/run, request) with concrete flags and a full proxy-options table, covering the common cases fully.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the "skip to Step 2" reference points to a step that is never labeled, a minor sequencing gap that caps it at 4.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections with no nested references, but everything is inlined in a ~150-line SKILL.md with no bundle files; at this length the proxy-options table and action reference could be split out, leaving it just below the ideal split.	4 / 5
	Total	16 / 20 Passed

Description

71%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.

A focused, product-specific description that clearly names the domain and resources and includes an explicit use-when clause. Its main weakness is thin trigger-term variety, relying almost entirely on the product name.

Suggestions

Add natural trigger phrases users would say, e.g. "email marketing, campaigns, broadcasts, contact lists" to broaden trigger-term coverage.

Replace the generic verb "Manage" with a few discrete actions (create, update, search, send) to lift specificity toward 5.

Tighten the "Use when" clause with concrete intents ("Use when the user wants to send broadcasts, manage contacts, or build automations in Sendlane").

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Lists, Tags, Broadcasts, Automations and more" enumerates several concrete resource types with broad coverage, though "Manage" is a generic catch-all verb rather than discrete actions, keeping it just below a 5.	4 / 5
Completeness	It states both the "what" (manage Persons/Organizations/Lists/etc.) and an explicit "when" ("Use when the user wants to interact with Sendlane data"), but the trigger clause is generic rather than packed with concrete trigger phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	The only natural keyword is "Sendlane" (repeated as "Sendlane data"); common synonyms users would actually say (email marketing, campaigns, contacts, broadcasts) are missing, matching the anchor with some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Sendlane" gives it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/sendlane/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.