Name: email-verifier-api
Rating: 52.8 (1 reviews)
Author: membranedev

email-verifier-api

Email Verifier Api integration. Manage data, records, and automate workflows. Use when the user wants to interact with Email Verifier Api data.

Quality

59%

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

Quality

Content

77%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 highly actionable with concrete CLI commands and a well-sequenced connection workflow including polling and error-recovery checkpoints. Its main weaknesses are some concept re-explanation, a broken "1b" heading, and a truncated docs URL.

Suggestions

Remove the introductory paragraph explaining what an email verifier is, and fix the truncated "Official docs: https://www.email" link.

Renumber the connection steps coherently (the "#### 1b." heading has no matching 1a), or convert the sequence into a numbered list.

Consider moving the full clientAction state spec and the proxy-flags table into a separate reference file to keep SKILL.md lean.

Dimension	Reasoning	Score
Conciseness	It is mostly efficient with concrete commands, but the opening "Email Verifier API is a tool that allows developers to verify the deliverability..." restates domain concepts Claude already knows, and the truncated "Official docs: https://www.email" line plus an orphaned "#### 1b." heading add noise.	3 / 5
Actionability	It provides concrete executable commands throughout (install, login, connection ensure with --wait, action list/run with --input JSON, request proxy) and a flags table, with only minor gaps like unresolved CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The connect -> wait/poll -> search -> run sequence has real validation checkpoints and a CLIENT_ACTION_REQUIRED feedback loop, but the orphaned "#### 1b." heading (with no 1a) breaks the top-level numbering and is a minor sequencing gap.	4 / 5
Progressive Disclosure	With no bundle files, the single SKILL.md is organized into clear sections (Overview, Working with, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); the inlined clientAction spec and proxy flags table could be split out but the structure is otherwise good.	4 / 5
	Total	15 / 20 Passed

Description

41%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 includes an explicit use-trigger and names a distinct product, but its action language is generic and it lacks the natural trigger terms a user would say when needing email verification. Tightening the capability verbs and adding concrete trigger phrases would lift it most.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete email-verification actions such as "Verify the deliverability and validity of email addresses."

Add natural trigger terms users say, e.g. "Use when the user wants to verify an email address, check deliverability, reduce bounce rates, or validate an email list."

Drop generic verbs like "manage data" and "records" that overlap with broad data-management skills and dilute distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase "Manage data, records, and automate workflows" uses generic verbs with no concrete email-verification actions (no mention of verifying deliverability or validating addresses), so it only names the domain with minimal/generic actions.	2 / 5
Completeness	An explicit "Use when the user wants to interact with Email Verifier Api data" trigger is present, but the "what" ("Manage data, records, and automate workflows") is vague rather than concrete, so it sits at the clear-when / weak-what boundary.	3 / 5
Trigger Term Quality	It repeats the brand name "Email Verifier Api" but omits the natural phrases users actually say ("verify email", "check deliverability", "bounce rate", "email validation"), leaving only generic terms.	2 / 5
Distinctiveness Conflict Risk	Naming the specific product "Email Verifier Api" gives it a clear niche with minimal conflict risk, though the generic "manage data, records, automate workflows" tail creates minor overlap with broad data skills.	4 / 5
	Total	11 / 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/email-verifier-api/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.