Name: quickemailverification
Rating: 49.6 (1 reviews)
Author: membranedev

quickemailverification

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

Quality

54%

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/quickemailverification/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 content is actionable and well-structured, with executable commands, a clear connection workflow, and explicit validation/polling checkpoints. The main weaknesses are minor filler prose and placeholder-based examples rather than fully concrete ones.

Suggestions

Tighten or remove filler sentences like 'so you can focus on the integration logic rather than auth plumbing' to improve token efficiency.

Fix the inconsistent section numbering (e.g. the '1b' subsection and the referenced but unlabelled 'Step 2') so the workflow sequence is unambiguous.

Where possible, replace generic placeholders (QUERY, CONNECTION_ID) with a short worked example showing realistic values.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but contains a few padded or filler sentences (e.g. 'so you can focus on the integration logic rather than auth plumbing' and the awkward 'Those will be used to adjust tooling to be used best with your harness') that could be trimmed.	3 / 5
Actionability	It provides numerous concrete, executable commands with example JSON inputs and a flag table, covering the common cases; it stops short of fully copy-paste-ready examples because placeholders like QUERY and CONNECTION_ID are used throughout.	4 / 5
Workflow Clarity	The connect -> poll-until-ready -> search -> run sequence is clear, with an explicit state machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a feedback loop for re-polling after user action; minor gaps come from inconsistent section numbering ('1b', a referenced but unlabelled 'Step 2').	4 / 5
Progressive Disclosure	A single, well-organized SKILL.md with clearly signaled sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no bundle files; some fairly dense inline content (state-machine detail, flag table) keeps it just below the ideal split.	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 correctly identifies a clear niche and includes an explicit trigger clause, but its stated capabilities are generic ('manage data, records, automate workflows') rather than tied to concrete email-verification actions. Tightening the capability verbs and adding natural user keywords would lift specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete email-verification actions, e.g. 'verify email addresses, check deliverability, and clean email lists'.

Add natural trigger terms users actually say, such as 'email validation', 'reduce bounces', or 'email list cleaning'.

Make the 'when' clause more specific by referencing email-related tasks rather than generic 'data' interaction.

Dimension	Reasoning	Score
Specificity	Names the domain but the actions ('Manage data, records, and automate workflows') are generic and minimal, with no concrete email-verification capabilities like validating addresses or checking deliverability.	2 / 5
Completeness	It includes an explicit 'Use when...' clause and a 'what' statement, but the 'what' is vague ('Manage data, records, and automate workflows') and the 'when' is generic, leaving it below the level of a clearly specified both-what-and-when description.	3 / 5
Trigger Term Quality	Keywords ('QuickEmailVerification', 'data', 'records', 'workflows') are mostly generic and miss the natural phrases users say such as 'verify emails', 'email validation', 'bounce', or 'email list'.	2 / 5
Distinctiveness Conflict Risk	The 'QuickEmailVerification integration' niche and its data-interaction trigger are mostly distinct, with only minor overlap risk against other generic data-management 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/quickemailverification/SKILL.md
Commit: f484c82

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