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

Blog Docs Log in Get started

enormail

Enormail integration. Manage Mailboxs, Campaigns. Use when the user wants to interact with Enormail data.

Quality

73%

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

Quality

Content

72%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 throughout and a clear, well-structured single-file layout. Its main weakness is workflow clarity: destructive and batch operations lack validation or verification steps, which caps that dimension.

Suggestions

Add an explicit verification/validation checkpoint before destructive operations such as delete-list and delete-contact (e.g. confirm the list/contact exists and warn the user before deletion).

Add a verification step after send-mailing (e.g. poll get-mailing-statistics or check state) so the send workflow has a feedback loop.

Trim redundant restatements of the connection-ready flow across the 'Connecting to Enormail' and '1b' sections to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it includes some redundant explanation (e.g. restating the connection-ready flow across 'Connecting' and '1b') and boilerplate that could be tightened, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for every step (install, login, connection ensure, action list/run, proxy requests) with flags and JSON examples, fully covering the common cases.	5 / 5
Workflow Clarity	A clear multi-step sequence exists for connecting and running actions, but destructive and batch operations (delete-list, delete-contact, send-mailing) have no validation or verification checkpoint, which caps this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is a single file, but it is well-organized into clearly signaled sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices), so the simple-skill exception yields a 5.	5 / 5
	Total	16 / 20 Passed

Description

75%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 complete with an explicit 'Use when' trigger and a distinct, branded niche. It is weakest in specificity and trigger-term quality, where only two concrete actions and generic 'interact with data' phrasing leave room for richer, more natural keyword coverage.

Suggestions

Expand the capability list beyond 'Mailboxs, Campaigns' to include concrete actions like create/send mailings, manage contacts, and retrieve statistics so specificity reaches comprehensive coverage.

Replace the generic 'interact with Enormail data' with natural user phrases such as 'send email campaigns', 'manage mailing lists', or 'view mailing statistics' to improve trigger-term quality.

Fix the typo 'Mailboxs' to 'Mailboxes' for professionalism.

Dimension	Reasoning	Score
Specificity	The description names the domain (Enormail) and two concrete actions ('Manage Mailboxs, Campaigns') but is not comprehensive, matching the anchor for naming the domain with 1-2 concrete actions.	3 / 5
Completeness	It clearly states what the skill does ('Enormail integration. Manage Mailboxs, Campaigns.') and provides an explicit trigger clause ('Use when the user wants to interact with Enormail data.'), satisfying both what and when with a concrete trigger phrase.	5 / 5
Trigger Term Quality	It relies on the generic phrase 'interact with Enormail data' with the brand name as the main keyword; it lacks common variations or synonyms users would naturally say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product (Enormail) with branded triggers gives it a clear niche with minimal conflict risk against 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/enormail/SKILL.md
Commit: f484c82

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