Name: mailmodo
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mailmodo

Mailmodo integration. Manage Campaigns, Users, Reports. Use when the user wants to interact with Mailmodo data.

Quality

63%

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

Quality

Content

61%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 provides strong, executable command coverage for connecting to and acting on Mailmodo via the Membrane CLI with good section organization. Its weak points are a padded marketing intro, missing validation for batch/destructive actions, and a broken step reference.

Suggestions

Add a verification step after running batch or destructive actions (e.g., check the response 'output' field for success/error before proceeding).

Trim the marketing intro paragraph about Mailmodo's audience and AMP emails, keeping only operationally relevant context.

Fix the 'skip to Step 2' reference by numbering the connection workflow steps consistently or removing the dangling pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational commands, but the marketing intro ('used by marketers and businesses looking to improve engagement and conversions through AMP emails') explains product context Claude does not need, fitting anchor 3 rather than the leaner 4.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (install, login, connection ensure, action list/run, request proxy), but minor gaps like the empty Description column in the actions table and the <agentType> placeholder keep it at anchor 4 rather than 5.	4 / 5
Workflow Clarity	The connection flow has state-checking and polling checkpoints, but batch/destructive operations (bulk-add-contacts, abort-journey, trigger-campaign) run without any validation or verification step, which caps workflow clarity at 3 per the batch/destructive guideline.	3 / 5
Progressive Disclosure	The single file is well-organized into clear sections and needs no external bundle references, but a dangling 'skip to Step 2' reference with no matching Step 2 header is a minor organization gap, fitting anchor 4 rather than 5.	4 / 5
	Total	14 / 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 clearly names the target app and provides both a capability summary and a use-when clause, with low conflict risk. Its main weakness is generic verb choice and limited trigger-term variation.

Suggestions

Replace the generic verb 'Manage' with concrete actions (e.g., 'Create and send campaigns, manage contact lists, fetch campaign reports').

Expand the trigger clause with natural variations (e.g., 'Use when the user wants to send email campaigns, manage Mailmodo contacts, or pull campaign reports').

Align the listed entities with the body ('Contacts'/'Lists'/'Journeys' rather than 'Users').

Dimension	Reasoning	Score
Specificity	Names the domain (Mailmodo) and lists entities ('Manage Campaigns, Users, Reports'), but 'Manage' is a generic verb rather than concrete actions, so it sits at anchor 3 and not 4.	3 / 5
Completeness	Both 'what' ('Manage Campaigns, Users, Reports') and 'when' ('Use when the user wants to interact with Mailmodo data') are explicit, but the 'when' could be more specific, matching anchor 4 and not the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The 'Mailmodo' keyword and phrase 'interact with Mailmodo data' are present, but common variations or synonyms are missing, fitting anchor 3 rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	'Mailmodo' is a specific named application giving it a clear niche with distinct triggers and minimal conflict risk, matching anchor 5.	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/mailmodo/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.