Name: moosend
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

moosend

Moosend integration. Manage Campaigns, Templates, Automations. Use when the user wants to interact with Moosend data.

Quality

69%

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

Quality

Content

65%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 skill is highly actionable with executable CLI commands and a solid connection-state feedback loop, but it bloats the context window with an unnecessary marketing intro and a large inline action reference while omitting validation steps for destructive and batch operations.

Suggestions

Trim the opening paragraph ("Moosend is an email marketing automation platform. It's used by businesses of all sizes...") and the "burn less tokens" phrasing; Claude does not need the market positioning.

Add an explicit validation/confirmation checkpoint before destructive and batch actions (e.g., confirm the mailing list ID with the user before remove-subscriber, or run a get-* detail call to verify the target before delete-campaign/delete-mailing-list).

Move the popular-actions table into a separate references file (e.g. ACTIONS.md) and keep SKILL.md as an overview that links to it, so the action catalog does not consume the context window by default.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens with marketing-style padding ("It's used by businesses of all sizes to create, send, and track email campaigns...") and includes filler like "burn less tokens and make communication more secure" that assumes less competence than warranted.	3 / 5
Actionability	Commands are copy-paste ready with real flags and package names (e.g. `npm install -g @membranehq/cli@latest`, `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json`) and cover the common cases of login, connect, search, run, and proxy.	5 / 5
Workflow Clarity	The connection flow has a genuine feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but destructive/batch actions like delete-campaign, remove-subscriber, and add-multiple-subscribers are executed with no validation or confirmation step, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Section structure is clear, but the 20-row popular-actions reference table is inlined content that belongs in a separate reference file, and there are no bundle files or external file references to offload the bulk.	3 / 5
	Total	14 / 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 a distinct product niche with both a what and a when clause, but its action verb is generic and its trigger terms omit several core Moosend concepts users would naturally mention.

Dimension	Reasoning	Score
Specificity	It names the domain and three entities ("Manage Campaigns, Templates, Automations"), but the single generic verb "Manage" applied to nouns is less concrete than listing several distinct actions, so it sits at anchor 3 rather than 4.	3 / 5
Completeness	Both a clear "what" ("Moosend integration. Manage Campaigns, Templates, Automations.") and an explicit "when" ("Use when the user wants to interact with Moosend data.") are present, but the trigger is a single broad phrase that could be more specific.	4 / 5
Trigger Term Quality	Natural keywords Moosend, Campaigns, Templates, and Automations are present with an explicit trigger clause, but core terms a user would say like "subscribers", "mailing lists", and "email marketing" are missing, matching anchor 4.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product Moosend with a Moosend-scoped trigger gives it a clear niche with minimal overlap risk against 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/moosend/SKILL.md
Commit: f484c82

Reviewed: 5 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.