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

Blog Docs Log in Get started

mailbluster

Mailbluster integration. Manage Campaigns, Templates. Use when the user wants to interact with Mailbluster 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/mailbluster/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 tight, command-heavy CLI usage guide with strong actionability and a well-sequenced connection workflow. It is held back mainly by a marketing-flavored intro and the absence of post-action verification and a concrete Mailbluster example.

Suggestions

Trim the opening marketing paragraph (Amazon SES affordability, target audiences) since it does not aid execution.

Add one concrete end-to-end example (e.g. discovering and running an action to create/send a campaign) so the run flow is copy-paste ready beyond placeholders.

Add a verification step after running actions (e.g. check the response `output` field / `state` for success) to close the workflow validation gap for potentially destructive campaign operations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but the opening marketing paragraph ("focused on affordability by utilizing Amazon SES... designed for bloggers, e-commerce stores, and non-profits") and a few explanatory asides are unnecessary context Claude does not need.	3 / 5
Actionability	Concrete, executable commands are given throughout (install, login, connection ensure, action list/run, request) plus a flags table, but examples use placeholders (<actionId>, CONNECTION_ID) and lack a specific end-to-end Mailbluster example such as creating a campaign, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow is a clear sequenced state machine with polling and CLIENT_ACTION_REQUIRED feedback loops, but "skip to Step 2" references an unlabeled step and there is no verification step after running actions, which are minor validation gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Working with Mailbluster, Popular actions, Best practices) with no nested references, though at ~140 lines some detail (the connection state machine, flags table) is inlined rather than split into a reference file.	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 answers both what and when using third-person voice, but its trigger guidance is generic and its capability list is narrow. Tightening the when-clause and adding common synonyms would raise it.

Suggestions

Replace the generic trigger with concrete ones, e.g. "Use when the user wants to create or send email campaigns, manage subscribers and lists, or design email templates in Mailbluster."

Expand the capability list beyond Campaigns and Templates to include the other surfaced entities (Lists, Subscribers, Segments) for fuller coverage.

Add natural synonyms/file or platform terms users actually say (e.g. "email campaigns", "newsletters", "subscriber lists") to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	Names the Mailbluster domain and two concrete entities ("Manage Campaigns, Templates"), but the verb "Manage" is generic and coverage of the platform's capabilities (lists, subscribers, segments) is not comprehensive, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	Both "what" ("Mailbluster integration. Manage Campaigns, Templates.") and "when" ("Use when the user wants to interact with Mailbluster data") are present, but the when-clause names the app generically rather than specifying concrete triggers, so it is not a 5.	4 / 5
Trigger Term Quality	Relevant keywords ("Campaigns", "Templates", "Mailbluster") are present, but the trigger "interact with Mailbluster data" is generic and omits common natural variations like "email campaigns", "subscribers", "lists", or "newsletters".	3 / 5
Distinctiveness Conflict Risk	The named "Mailbluster" trigger gives it a clear niche with minimal conflict risk, but the generic "manage campaigns/templates" actions could overlap with other email-marketing integration skills, keeping it just below 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/mailbluster/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.