Name: mailersend
Rating: 64 (1 reviews)
Author: membranedev

mailersend

Mailersend integration. Manage Emails, Templates, Domains, Recipients, Activities. Use when the user wants to interact with Mailersend data.

Quality

76%

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

Quality

Content

80%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 content is highly actionable with executable commands across the whole workflow and well-structured single-file organization. The main gaps are minor introductory padding and the absence of explicit validation/confirmation steps for destructive or batch action runs.

Suggestions

Add an explicit validation or confirmation step before destructive or batch action runs (e.g., confirm with the user before sending emails or deleting domains, or dry-run where supported) to lift workflow clarity above the destructive-operation cap.

Trim the opening 'Mailersend is an email marketing platform...' paragraph and editorial phrases like 'so you can focus on the integration logic rather than auth plumbing' that restate what Claude already knows.

Clarify the agent-type placeholder in `membrane login --tenant --clientName=<agentType>` with a concrete example (e.g., `--clientName=claude`) so the install/login step is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands throughout, but the opening platform-description paragraph ('Mailersend is an email marketing platform that allows businesses...') and a few editorial phrases ('so you can focus on the integration logic rather than auth plumbing') are removable padding Claude already knows.	4 / 5
Actionability	Every step is backed by copy-paste-ready, executable commands (npm install, membrane login, connection ensure, action run with --input JSON, request proxy flags), and the proxy options table covers the common cases completely.	5 / 5
Workflow Clarity	The install→login→connect→poll→run sequence is clearly laid out with state-branching feedback loops (READY / CLIENT_ACTION_REQUIRED / error), but destructive or batch operations (sending emails, deleting domains) lack explicit validation or confirmation checkpoints, which caps workflow clarity at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	The single SKILL.md is cleanly organized into Overview, Working with Mailersend, Popular actions, and Best practices with clear section headers and no nested references, making navigation easy with no bundle files needed.	5 / 5
	Total	17 / 20 Passed

Description

73%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 clearly identifies the product and its core objects and provides an explicit 'Use when' clause, making it distinct and reasonably complete. Its main weakness is a single generic 'Manage' action verb and a trigger clause that could name more concrete user intents.

Suggestions

Replace or expand the generic 'Manage' verb with specific actions (e.g., 'Send transactional and marketing emails, create and update templates, verify domains') to improve specificity.

Make the trigger clause more concrete (e.g., 'Use when the user wants to send or schedule emails, manage templates, or verify sending domains in Mailersend') to strengthen completeness and trigger-term coverage.

Add natural synonyms a user might say, such as 'transactional email', 'email campaigns', or 'email delivery', to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Mailersend domain plus five concrete objects ('Emails, Templates, Domains, Recipients, Activities'), but the only action verb is the generic 'Manage', so concrete actions are not comprehensively enumerated.	3 / 5
Completeness	Explicitly states what it does ('Manage Emails, Templates, Domains, Recipients, Activities') and when to use it ('Use when the user wants to interact with Mailersend data'), but the 'when' clause is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural product name 'Mailersend' plus entity terms (Emails, Templates, Domains, Recipients, Activities), giving good keyword coverage, though it lacks synonyms like 'transactional email' or 'email campaigns'.	4 / 5
Distinctiveness Conflict Risk	The branded 'Mailersend integration' framing with a product-anchored trigger gives it a clear niche with minimal risk of firing for unrelated 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/mailersend/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.