Name: elastic-email
Rating: 63.2 (1 reviews)
Author: membranedev

elastic-email

Elastic Email integration. Manage Users, Contacts, Campaigns, Automations, Suppressions, Domains and more. Use when the user wants to interact with Elastic Email data.

Quality

75%

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

Quality

Content

78%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 executable CLI commands and a clear connection-to-actions workflow including state-based branching. It is slightly verbose in places and inlines reference-style material that could live in separate files.

Suggestions

Move the 16-row popular-actions table and proxy-flag reference into a separate references file and link to it from the body to improve progressive disclosure.

Trim the platform-overview paragraph and the Membrane-auth narrative, which restate context Claude can infer from the commands.

Add an explicit verify step before destructive actions (delete-contact, delete-contact-list, delete-template), e.g. confirm the target by listing first.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven guidance with minimal concept explanation, though sections like the platform overview and Membrane-auth narrative add some padding that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready CLI commands for install, login, connection, action search/run, and proxy requests with concrete flags and a parameter example, covering the common cases fully.	5 / 5
Workflow Clarity	The connect-to-actions sequence is clearly laid out with a polling checkpoint and state-driven branching (READY/CLIENT_ACTION_REQUIRED/error), but batch/destructive operations like delete-contact lack explicit validation steps.	4 / 5
Progressive Disclosure	Structure is sectioned and there are no broken nested references, but all content is inlined in one file with no bundle files used to offload the lengthy popular-actions table and proxy-flag reference.	3 / 5
	Total	16 / 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 identifies a distinct product niche and lists concrete managed entities, with an explicit Use-when clause. Its main weakness is a generic trigger phrase rather than natural, varied user keywords.

Suggestions

Expand the trigger phrase beyond 'interact with Elastic Email data' to natural user terms like 'sending campaigns, managing contacts, or working with Elastic Email lists'.

Replace the generic verb 'Manage' with more specific actions per entity (e.g., 'create and send campaigns, add and update contacts, manage suppressions').

Consider adding 'Use when the user mentions Elastic Email, email campaigns, or contact lists' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Elastic Email) and several concrete management actions ("Manage Users, Contacts, Campaigns, Automations, Suppressions, Domains"), giving good but somewhat generic action coverage compared to the score-5 anchor's fuller enumeration.	4 / 5
Completeness	It states clearly what the skill does and includes a "Use when the user wants to interact with Elastic Email data" clause, but the when-side is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	"interact with Elastic Email data" is the only natural trigger phrase; it lacks the synonyms and concrete user phrases (campaigns, contacts, email lists) that would mark comprehensive keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The Elastic Email product niche and named entities are highly specific, making conflict with unrelated skills minimal and triggers clearly product-bound.	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/elastic-email/SKILL.md
Commit: f484c82

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