Name: inxmail
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

inxmail

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

Quality

61%

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

Quality

Content

65%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, executable commands and a strong connection workflow, but it is padded with marketing background, lacks validation guidance for destructive operations, and inlines bulk reference content that should be a separate file.

Suggestions

Remove or condense the introductory marketing description of what Inxmail is; assume Claude knows the platform category.

Add a validation/verification step for destructive actions (e.g. confirm the resource exists and re-fetch after delete) so destructive workflows are not uncapped.

Move the Popular actions table into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and reference, but the opening marketing description ("Inxmail is an email marketing automation platform...helps marketers manage subscribers, personalize content, and analyze campaign performance") and some verbose connection-state explanations are unnecessary padding Claude could infer.	3 / 5
Actionability	It provides copy-paste ready, executable commands for install, login, connection ensure, action list/run with JSON input, and proxy requests, plus a flags table and a concrete actions table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with polling checkpoints and CLIENT_ACTION_REQUIRED feedback loops, but the skill exposes destructive operations (delete-recipient, delete-mailing-list, delete-target-group) with no validation or verification steps, capping this dimension.	3 / 5
Progressive Disclosure	Sections are reasonably organized, but no bundle files exist and the 20-row Popular actions table is bulk reference content inlined in SKILL.md that would be better split into a separate reference file.	3 / 5
	Total	14 / 20 Passed

Description

57%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 answers both what and when with an explicit Use-when clause and a distinct brand trigger, but its action language is generic and the trigger terms lack concrete variations.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Inxmail actions such as "list mailing lists, create and send mailings, manage recipients and target groups".

Expand the trigger clause with concrete phrases users would say, e.g. "Use when the user wants to manage Inxmail mailing lists, recipients, sendings, or campaigns".

Dimension	Reasoning	Score
Specificity	It names the Inxmail domain, but the listed actions ("Manage data, records, and automate workflows") are generic verbs rather than concrete capabilities, fitting the anchor where actions are minimal or generic.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Inxmail data") are present, though the trigger could be more specific with concrete phrases.	4 / 5
Trigger Term Quality	"Inxmail" / "Inxmail data" / "Inxmail integration" provide the core natural keyword a user would say, but there are no synonyms or variations beyond the brand name, matching the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The Inxmail brand name gives it a clear niche with minimal conflict risk, but the generic action verbs ("manage data, records, automate workflows") could overlap with other email/marketing integration skills.	4 / 5
	Total	13 / 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/inxmail/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.