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

mailerlite

Mailerlite integration. Manage Subscribers, Campaigns, Forms, Websites. Use when the user wants to interact with Mailerlite 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/mailerlite/SKILL.md

Quality

Content

68%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 copy-paste CLI commands and a well-structured connection workflow, but it wastes tokens on an explanatory intro and a blank-description actions table, and it lacks validation guidance around destructive actions. Filling the table descriptions and adding a verify step for deletes would raise the score.

Suggestions

Add a validation/verification checkpoint before destructive actions, e.g. confirm the target subscriber/group id and re-fetch to verify the delete succeeded.

Trim the introductory paragraph defining Mailerlite (Claude can infer this) and either fill the blank 'Description' column of the Popular actions table or move the table to a separate reference file.

Resolve the dangling 'Step 2' reference in the connection flow (there is no labeled Step 1/Step 2) so the skip-ahead instruction is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the introductory paragraph explaining what Mailerlite is and the 20-row 'Popular actions' table with blank Description columns add padding that could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands for install, login, connection, action search, action run (with JSON input), and proxy requests, covering the common cases.	5 / 5
Workflow Clarity	The connection flow has clear state-based checkpoints and polling feedback, but running destructive actions (Delete Subscriber/Campaign/Group/Field) has no validation or verification step, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references and is self-contained; minor gaps are the inline 20-row actions table that could live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

70%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 is well-formed with an explicit 'Use when' trigger and a clear named domain, but it relies on a single generic verb ('Manage') and a somewhat vague trigger condition. Tightening the action verbs and making the trigger more concrete would lift it into the top band.

Suggestions

Replace the generic 'Manage' with concrete verbs, e.g. 'Create, update, and delete Subscribers, Campaigns, Forms, and Websites'.

Make the trigger phrase more specific, e.g. 'Use when the user wants to manage email subscribers, campaigns, or forms in Mailerlite'.

Add a natural synonym or file/URL cue (e.g. 'Mailerlite API' or 'mailerlite.com') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete resource types (Subscribers, Campaigns, Forms, Websites) but the only action verb is the generic 'Manage', so concrete actions are minimal rather than comprehensive.	3 / 5
Completeness	Explicitly answers both 'what' (Mailerlite integration managing those resources) and 'when' via a 'Use when the user wants to interact with Mailerlite data' clause, but the 'when' is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	Includes natural domain terms users would say ('Mailerlite', 'Subscribers', 'Campaigns', 'Forms', 'Websites') with good coverage, though a few common synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a specific named platform (Mailerlite) giving it a clear niche with minimal conflict risk, but the trigger phrasing ('interact with Mailerlite data') is broad enough to leave minor overlap with generic data skills.	4 / 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/mailerlite/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.