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

mailify

Mailify integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Mailify data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/mailify/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.

A well-structured, command-rich integration guide with a genuinely strong connection-state feedback loop, weakened by filler prose, a redundant "Popular actions" section, and missing verification steps around destructive proxy operations. Actionability is high but stops short of fully worked examples.

Suggestions

Delete the filler line "Use action names and parameters as needed." and the redundant "Popular actions" section, or replace it with 2-3 actual common actions with concrete example invocations.

Add a verification step after running actions and before destructive proxy calls (e.g. confirm the returned `output`/status before proceeding with PUT/DELETE requests).

Trim the opening "Mailify is an email marketing platform..." paragraph to one line, since Claude can infer the niche from the brand and official docs link.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (commands and a flag table), but includes filler ("Use action names and parameters as needed"), a redundant "Popular actions" section that re-states the discovery command, and an explainer paragraph on what Mailify is that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy with concrete flag examples; the gap is the "Popular actions" section, which promises popular actions but only repeats the discovery command with no worked example.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit state-based feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, check error on CONFIGURATION_ERROR/SETUP_FAILED), but running actions and destructive proxy methods (PUT/DELETE) lack verification checkpoints.	4 / 5
Progressive Disclosure	There are no bundle files and all content is inline, but it is organized into clear, well-labeled sections (Overview, Install, Auth, Connecting, Searching, Running actions, Proxy, Best practices) with minor organization gaps; at ~140 lines some reference material could be split out.	4 / 5
	Total	15 / 20 Passed

Description

70%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.

A solid description that explicitly pairs a "what" with a "Use when" trigger and names concrete domain entities, but it relies on the generic verb "Manage" and a vague trigger clause rather than concrete actions and trigger phrases. It is clearly distinct via the Mailify brand name with only minor overlap risk.

Suggestions

Replace the generic "Manage" with concrete actions, e.g. "Create and update Persons, Organizations, Deals, Leads, Activities, and Notes".

Expand the "Use when" clause with concrete trigger phrases, e.g. "Use when the user wants to create deals, log activities, or manage contacts and organizations in Mailify."

Drop the trailing "and more" — it dilutes specificity without adding a triggerable keyword.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Mailify integration") and lists concrete entities ("Persons, Organizations, Deals, Leads, Activities, Notes"), but the only action verb is the generic "Manage", so actions are minimal rather than comprehensive.	3 / 5
Completeness	It answers both "what" ("Mailify integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes...") and "when" ("Use when the user wants to interact with Mailify data"), but the "when" clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces natural keywords a user would say ("Mailify", "Deals", "Leads", "Persons", "Organizations", "Activities", "Notes") with good coverage; a few common synonyms or phrasings are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The named brand "Mailify" gives it a clear niche with minimal conflict risk, but the generic "Manage... and more" plus CRM-style entity terms (Deals, Leads) create minor overlap with related CRM/contact skills.	4 / 5
	Total	15 / 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/mailify/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.