Name: mailcheck
Rating: 48.8 (1 reviews)
Author: membranedev

mailcheck

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

Quality

52%

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/mailcheck/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 solid, executable integration guide with clear CLI commands, a sequenced connection-readiness workflow, and good sectioning. It loses points for introductory explanation Claude already knows, a dangling 'Step 2' reference, and a thin Overview stub.

Suggestions

Trim the introductory paragraph explaining what Mailcheck is and why developers use it; Claude already knows this and it competes with context.

Fix the dangling 'Step 2' reference (the text jumps to '1b' and 'Step 2' without defining Step 2) so the connection workflow is self-consistent.

Remove or fill in the empty 'Mailcheck Overview' bullet list ('Email / Analysis / Settings'), which adds no actionable information.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-pasteable CLI commands, but it includes explanations Claude already knows (e.g. 'Mailcheck is a service that suggests corrections... improves email deliverability and reduce user errors') and padded prose around Membrane, so it could be tightened.	3 / 5
Actionability	It provides concrete, executable commands for install, login, connection ensure/get, action list/run, and proxy requests with flag tables and JSON examples; only minor gaps remain (e.g. action discovery is shown twice with slightly different invocations and CONNECTION_ID is never concretely obtained).	4 / 5
Workflow Clarity	The connect-to-ready flow is clearly sequenced with polling and an explicit state machine (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), giving built-in validation checkpoints; minor gaps include a stray 'Step 2' reference with no Step 2 defined and duplicated action-list guidance.	4 / 5
Progressive Disclosure	Content is well sectioned (Overview, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files to split out; structure is good but the 'Mailcheck Overview' stub ('Email / Analysis / Settings') adds little and could be removed or filled in.	4 / 5
	Total	15 / 20 Passed

Description

37%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 identifies the integration and includes a 'Use when' clause, but the stated capabilities are generic ('manage data, records, automate workflows') rather than concrete Mailcheck actions, and the trigger phrasing repeats the product name instead of natural user language. It is functional but padded with vague verbs.

Suggestions

Replace generic verbs with concrete Mailcheck capabilities, e.g. 'Suggest corrections for misspelled email addresses and fetch domain suggestions from Mailcheck.'

Rewrite the 'when' clause in natural user terms, e.g. 'Use when the user wants to catch email typos in a signup/checkout form or needs Mailcheck domain suggestions.'

Drop vague filler like 'Manage data, records, and automate workflows' that does not describe anything Mailcheck-specific.

Dimension	Reasoning	Score
Specificity	The description names the domain (Mailcheck) and lists generic verbs ('Manage data, records, and automate workflows') but no concrete Mailcheck-specific actions; 'data' and 'records' are vague abstractions rather than real capabilities like email correction or domain suggestion.	2 / 5
Completeness	There is a weak 'what' (manage data/records, automate workflows) and an explicit 'when' clause ('Use when the user wants to interact with Mailcheck data'), but the 'what' is abstract and the 'when' restates the skill name rather than giving concrete trigger conditions, so it does not clearly answer both.	3 / 5
Trigger Term Quality	It surfaces 'Mailcheck' and 'interact with Mailcheck data' but omits the natural terms users say (email address, misspelling, typo, suggestion, autocomplete, signup/checkout); the trigger 'wants to interact with Mailcheck data' is generic rather than phrased as a user need.	2 / 5
Distinctiveness Conflict Risk	The Mailcheck name gives it some distinctiveness, but 'Manage data, records, and automate workflows' is so broad it could plausibly overlap with many integration/data skills, leaving moderate conflict risk.	3 / 5
	Total	10 / 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/mailcheck/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.