Name: mailcoach
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

mailcoach

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

Quality

66%

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/mailcoach/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 is highly actionable with concrete Membrane CLI commands and a clear connection-state workflow, but it is padded with marketing prose, lacks validation steps around destructive operations, and inlines content that could be split into references.

Suggestions

Trim the introductory marketing paragraph and the "focus on the integration logic rather than auth plumbing" aside to only what Claude needs to act.

Add a validation/checkpoint step before destructive operations, e.g. confirm the action or method (DELETE) with the user and verify the response state before proceeding.

Fix the broken "skip to Step 2" reference by labeling the next section as Step 2 or removing the cross-reference.

Dimension	Reasoning	Score
Conciseness	Most of the body is executable commands, but the intro marketing paragraph ("self-hosted email marketing platform... without relying on third-party services") and prose like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for install, login, connection, action search/run, and proxying, but commands rely on placeholders (CONNECTION_ID, QUERY) and there is no worked end-to-end example with real input and parsed output.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state-check checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive-capable operations (action run, proxy DELETE) lack validation steps and the "skip to Step 2" reference points to no explicit Step 2.	3 / 5
Progressive Disclosure	No bundle files exist and content is organized into clear sections (Overview, Authentication, Connecting, Searching, Proxy, Best practices), but at ~140 lines all material is inlined with no one-level-deep references for the proxy flag table or connection-state details.	4 / 5
	Total	14 / 20 Passed

Description

71%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 answers both what and when and targets a clearly distinct product niche. Its main weakness is a generic "Manage" verb and a when-clause that omits concrete trigger synonyms like campaigns, subscribers, or email lists.

Suggestions

Replace the generic verb "Manage" with concrete actions per entity, e.g. "Create and manage EmailLists, schedule Campaigns, edit Templates, and configure Automations".

Expand the trigger clause with natural phrases users say, e.g. "Use when the user mentions Mailcoach, email campaigns, subscriber lists, or email automations."

Add the file/extension or product synonyms (email marketing platform, self-hosted) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage Users, EmailLists, Campaigns, Templates, Automations" lists several specific Mailcoach entities giving comprehensive domain coverage, though the single verb "Manage" is generic rather than a set of distinct concrete actions.	4 / 5
Completeness	It states both what ("Manage Users, EmailLists, Campaigns, Templates, Automations") and when ("Use when the user wants to interact with Mailcoach data"), but the when-clause is generic and lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Mailcoach data" surfaces the core keyword "Mailcoach", but common synonyms a user might say (email marketing, campaigns, subscribers, email lists) are missing.	3 / 5
Distinctiveness Conflict Risk	Targeting the named product "Mailcoach" carves out a clear niche with distinct triggers and minimal overlap risk with unrelated 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/mailcoach/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.