Name: emaillistverify
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

emaillistverify

EmailListVerify integration. Manage Users. Use when the user wants to interact with EmailListVerify data.

Quality

69%

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

Quality

Content

88%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 a well-structured, highly actionable integration guide with executable commands and a clear, validated connection workflow. Its only weakness is minor verbosity in a few explanatory passages and some inline content that could be externalized.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with little padding, but includes a few trimmable explanatory passages (the "focus on the integration logic rather than auth plumbing" line and the clientAction field-by-field descriptions), matching the score-4 anchor; not 5 due to those minor over-explanations.	4 / 5
Actionability	Concrete, copy-paste-ready bash commands with parameter examples cover the common cases (install, login, connection ensure, action list/run, request proxy), matching the score-5 anchor.	5 / 5
Workflow Clarity	The connection setup is a clear sequence with explicit polling/validation checkpoints and feedback loops (poll until state changes, re-poll after a client action, branch on CONFIGURATION_ERROR/SETUP_FAILED), matching the score-5 anchor for an external/batch operation context.	5 / 5
Progressive Disclosure	A single, well-organized SKILL.md with clear section headers and no bundle files; the inline Popular actions table and API detail could be split out, leaving minor organization gaps that fit score 4 rather than 5.	4 / 5
	Total	18 / 20 Passed

Description

50%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 distinguishable and includes an explicit trigger clause, but its capability description is generic and its trigger keywords miss the natural terms users would say. Strengthening both would move it from adequate to strong.

Suggestions

Replace "Manage Users" with concrete capabilities, e.g. "Verify email addresses, check disposable domains and blacklists, find contact emails, and track bulk list verification jobs."

Expand the trigger to include natural phrasing: "Use when the user wants to verify emails, clean email lists, reduce bounce rates, or check email deliverability."

Add file-format or API keywords users actually say (e.g. "email verification", "email list cleaning", "bounce rate") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Users" names the domain but offers only a minimal, generic action with no concrete email-verification capabilities, matching the score-2 anchor; it is not entirely vague (not 1) and lacks 1-2 concrete actions (not 3).	2 / 5
Completeness	Both a "what" (EmailListVerify integration, Manage Users) and an explicit "Use when the user wants to interact with EmailListVerify data" trigger are present, matching score 4; it is not score 5 because neither the what nor the when is concrete or specific.	4 / 5
Trigger Term Quality	Only "EmailListVerify" and "EmailListVerify data" appear as keywords; the natural phrases users would say (verify emails, clean email list, bounce rate, deliverability) are missing, matching the score-2 anchor.	2 / 5
Distinctiveness Conflict Risk	"EmailListVerify integration" carves a clear niche with minimal conflict risk, but the generic "interact with EmailListVerify data" trigger leaves minor overlap risk, placing it at 4 rather than 5.	4 / 5
	Total	12 / 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/emaillistverify/SKILL.md
Commit: f484c82

Reviewed: 4 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.