Name: mailgun
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mailgun

Mailgun integration. Manage Mailboxs, Domains, Templates, Logs. Use when the user wants to interact with Mailgun data.

Quality

74%

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

Quality

Content

75%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 content is highly actionable with copy-paste-ready Membrane commands and a clear, state-aware connection workflow, weakened mainly by a padded introductory paragraph and the absence of reference files to externalize the large actions table. It is an efficient, well-structured skill body with minor trimming and structure opportunities.

Suggestions

Cut the opening "Mailgun is an email automation service..." paragraph and the "Use action names and parameters as needed" line; Claude already knows what Mailgun is.

Move the full "Popular actions" table into a references file (e.g. ACTIONS.md) and keep only a short representative subset inline, with a clear pointer.

Label the post-connection section explicitly as "Step 2" (or remove the "skip to Step 2" reference) so the workflow's stated checkpoints resolve to real sections.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but the opening paragraph explains what Mailgun is and who uses it (concepts Claude already knows), and filler like "Use action names and parameters as needed" could be trimmed, matching the mostly-efficient-but-some-unnecessary-explanation anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands (`membrane connection ensure`, `membrane action list`, `membrane action run`, proxy requests) with flags, JSON input examples, and a populated actions table covering the common cases.	5 / 5
Workflow Clarity	The install → authenticate → connect → wait-for-ready → search → run flow is clearly sequenced with state-based validation checkpoints and a poll-again feedback loop, but the "skip to Step 2" reference points to no labeled Step 2 and action-result validation is light, leaving a minor gap versus the anchor-5 example.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized with clear section headers and the inlined actions table serves discovery, but no reference files exist to offload the bulk action catalog, leaving minor organization gaps relative to the one-level-deep reference ideal.	4 / 5
	Total	16 / 20 Passed

Description

73%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 clear and distinct with both a what and a when clause, but its action vocabulary is limited to the generic verb "Manage" and its trigger phrasing could be more concrete. It is a solid, above-midpoint description with room to sharpen specificity.

Suggestions

Replace the generic "Manage" with concrete verbs per resource, e.g. "Send emails, manage Domains, Templates, Mailboxes, and Logs."

Expand the trigger clause with concrete phrases users say, e.g. "Use when the user wants to send or track emails, or manage Mailgun domains, templates, or logs."

Fix the typo "Mailboxs" to "Mailboxes" for cleaner trigger-term matching.

Dimension	Reasoning	Score
Specificity	It names the domain (Mailgun) and several concrete resources ("Mailboxs, Domains, Templates, Logs"), but the only action verb is the generic "Manage", so actions are minimal rather than comprehensive like the anchor-4 example's distinct verbs (extracts, fills, converts).	3 / 5
Completeness	It states both the "what" ("Manage Mailboxs, Domains, Templates, Logs") and an explicit "when" ("Use when the user wants to interact with Mailgun data"), but the trigger clause is somewhat generic and could be more specific, matching the anchor-4 example rather than the fully concrete anchor-5.	4 / 5
Trigger Term Quality	"Mailgun" plus the resource terms (Mailboxs, Domains, Templates, Logs) give good natural keyword coverage a user would actually say, though common synonyms like "email"/"send email" are missing.	4 / 5
Distinctiveness Conflict Risk	"Mailgun integration" carves a clear niche with a distinct brand trigger and minimal overlap risk with other 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/mailgun/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.