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

mailboxvalidator

MailboxValidator integration. Manage Users, Organizations. Use when the user wants to interact with MailboxValidator 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/mailboxvalidator/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 well-structured, actionable Membrane CLI guide with explicit state checkpoints and a polling feedback loop, held back by some explanatory padding, a duplicated command, and broken 'Step 2' cross-references.

Suggestions

Trim conceptual padding (the service definition paragraph and the 'focus on integration logic rather than auth plumbing' aside) since Claude can infer them.

Fix the dangling 'skip to Step 2' references by either adding a numbered Step 2 header or rewording to point at the 'Searching for actions' section.

De-duplicate the action-list command shown in both 'Searching for actions' and 'Popular actions', keeping a single canonical example.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation such as the service intro ('MailboxValidator is an email verification service...') and elaborations like 'so you can focus on the integration logic rather than auth plumbing', plus a repeated action-list command, so it could be tightened.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready bash commands for install, login, connection ensure, polling, action list/run, and proxy requests with a flags table — executable guidance with only minor gaps (placeholders like CONNECTION_ID and QUERY require substitution).	4 / 5
Workflow Clarity	The install → login → connect → poll-until-ready → search → run sequence is clear with explicit state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a polling feedback loop, but the dangling 'skip to Step 2' references (no Step 2 header exists) and lack of output verification are minor gaps.	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers with no nested or buried references, and the only external pointer is the official docs URL; the main gap is that all reference-style detail (clientAction schema, proxy flags) is inlined rather than split out, but the structure remains navigable.	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 covers what and when with a clear product niche, but the actions are generic and it lacks the natural trigger phrases (email verification, validation, bounce) that a user would actually say.

Suggestions

Replace generic 'Manage Users, Organizations' with concrete MailboxValidator actions like 'Verify email addresses, check deliverability, query credits'.

Strengthen the 'when' clause with natural triggers: 'Use when the user wants to verify emails, check if an address is deliverable, or reduce bounce rates'.

Add file/format cues users mention, e.g. '.csv lists of emails' or 'bulk email validation', to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('MailboxValidator integration') and two actions ('Manage Users, Organizations'), but the verb 'Manage' is generic and not comprehensive — matching the anchor that names a domain with 1-2 concrete but limited actions.	3 / 5
Completeness	It states both what ('Manage Users, Organizations') and when ('Use when the user wants to interact with MailboxValidator data'), but the 'when' clause is generic rather than a concrete trigger phrase, fitting the anchor where both are present but 'when' could be more specific.	4 / 5
Trigger Term Quality	It includes the product name and 'Users, Organizations', but misses the natural phrases a user would actually say (e.g. 'verify email', 'check email', 'bounce rate', 'email validation'), leaving only some relevant keywords without common synonyms.	3 / 5
Distinctiveness Conflict Risk	The named MailboxValidator product gives it a clear niche with minimal conflict risk, but the generic 'Users, Organizations' actions leave minor overlap with adjacent CRM/data skills rather than fully distinct triggers.	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/mailboxvalidator/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.