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

Blog Docs Log in Get started

mailercloud

Mailercloud integration. Manage Organizations, Users. Use when the user wants to interact with Mailercloud 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/mailercloud/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 well-structured, highly actionable guide to the Membrane CLI workflow with strong validation around the connection state machine, but it carries some marketing/boilerplate padding and offers generic CLI examples rather than Mailercloud-specific worked examples.

Suggestions

Cut the marketing intro ("used by businesses of all sizes to create, send, and automate email campaigns") and the filler line "Use action names and parameters as needed."; Claude already knows what email marketing platforms are.

De-duplicate the `membrane action list` command, which appears almost verbatim in both "Searching for actions" and "Popular actions".

Add at least one Mailercloud-specific worked example showing a real actionId, sample --input, and expected output (e.g. creating a campaign or listing subscribers) so the guidance is domain-concrete rather than CLI-generic.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary padding (the "used by businesses of all sizes" marketing intro, the "Use action names and parameters as needed" filler line) and redundantly repeats the `membrane action list` command in two sections.	3 / 5
Actionability	Provides copy-paste-ready CLI commands with real flags and a proxy-options table covering the common cases, but examples are generic CLI patterns with placeholders rather than a Mailercloud-specific worked example (no real actionId or sample output for an actual task).	4 / 5
Workflow Clarity	Clear sequence (install → login → connection ensure → wait → handle clientAction → search → run/proxy) with explicit validation checkpoints (state polling, CLIENT_ACTION_REQUIRED re-poll, CONFIGURATION_ERROR/SETUP_FAILED error handling), but the step numbering is inconsistent (a "1b" and an unlabeled "Step 2" reference).	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with easy navigation and no nested/2+-level references, but everything is inlined in one ~157-line file (feature tree, proxy flag table, clientAction details) with no bundle files to offload deeper material.	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 cleanly states what the skill does and when to use it with an explicit trigger, but the trigger and capabilities are generic — the real Mailercloud domain (email campaigns, subscribers, lists) is never mentioned, weakening trigger-term quality and specificity.

Suggestions

Replace generic "Manage Organizations, Users" with the concrete Mailercloud actions users actually request, e.g. "Create and send email campaigns, manage subscribers and lists, design email templates".

Expand the "Use when" clause with concrete trigger phrases such as "Use when the user wants to send campaigns, manage subscribers/lists, or design email templates in Mailercloud".

Add the natural synonyms and file/feature terms users say (campaigns, subscribers, segments, templates, automation) so the description surfaces for those intents.

Dimension	Reasoning	Score
Specificity	Names the domain (Mailercloud) and two concrete entities ("Manage Organizations, Users"), but the verb "Manage" is generic and the actual product domain (campaigns, subscribers, lists) is absent, so coverage is not comprehensive.	3 / 5
Completeness	Both a "what" ("Mailercloud integration. Manage Organizations, Users.") and an explicit "when" ("Use when the user wants to interact with Mailercloud data.") are present, but the trigger is generic rather than concrete phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Includes the brand keyword "Mailercloud" and a natural phrase ("interact with Mailercloud data"), but misses the common terms users would actually say (campaigns, subscribers, lists, templates, email marketing) that the body reveals.	3 / 5
Distinctiveness Conflict Risk	Tied to a named, distinctive product (Mailercloud) with low conflict risk, but the generic entities (Organizations, Users) could overlap with a generic user-management skill, keeping it just below a 5.	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/mailercloud/SKILL.md
Commit: f484c82

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