Name: reachmail
Rating: 64.8 (1 reviews)
Author: membranedev

reachmail

ReachMail integration. Manage Campaigns, Templates, Reports, Users, Roles. Use when the user wants to interact with ReachMail data.

Quality

78%

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

Quality

Content

76%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 highly actionable, well-structured skill with concrete commands and an excellent connection-state workflow. Its main gap is the absence of validation/verification steps for destructive or batch operations (sending campaigns, editing lists), which caps workflow clarity.

Suggestions

Add a validation/verification checkpoint before destructive or batch actions (e.g. confirm recipient list and dry-run/preview before sending a campaign; verify list changes after bulk edits).

Trim filler ('Use action names and parameters as needed.') and tighten the ReachMail overview paragraph to improve token efficiency.

Consider moving the proxy flag reference and action-discovery details into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Largely efficient with executable commands, but contains mild over-explanation (the ReachMail overview paragraph) and filler lines like 'Use action names and parameters as needed.' that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands for install, auth, connection, action discovery/execution, and proxying, with a clear flag table — fully executable across the common cases.	5 / 5
Workflow Clarity	The connection sub-flow is well-sequenced with explicit per-state polling and feedback loops, but running actions against an email-marketing system (campaign sends, list edits) has no validation/verification checkpoints for these destructive/batch operations, which caps the score at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is organized into clear sections with no nested references. Structure is good, though some proxy/discovery detail could optionally live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

80%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, concrete description that names specific capabilities and includes an explicit 'Use when' trigger. The main weakness is a generic 'when' clause and the absence of natural synonyms (email campaigns, subscribers, mailing lists) that users might say.

Suggestions

Replace the generic 'when the user wants to interact with ReachMail data' with concrete triggers, e.g. 'Use when the user wants to send email campaigns, manage subscribers or mailing lists, or pull ReachMail reports.'

Add natural synonyms and file-type hints (e.g. 'email campaigns, subscribers, templates, reports') so the skill triggers when users use everyday marketing vocabulary rather than the brand name.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities ('Manage Campaigns, Templates, Reports, Users, Roles'), giving comprehensive coverage of the integration's scope.	5 / 5
Completeness	Both 'what' (manage campaigns/templates/etc.) and 'when' are present and explicit, but the 'when' clause is generic ('interact with ReachMail data') rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes a natural trigger ('Use when the user wants to interact with ReachMail data') and named objects, but lacks common synonyms like 'email campaigns', 'subscribers', 'mailing lists', or file extensions.	4 / 5
Distinctiveness Conflict Risk	The ReachMail brand name gives a clear, distinct niche, though triggering depends on the brand being mentioned rather than on domain-specific triggers, leaving minor overlap risk with other email-marketing skills.	4 / 5
	Total	17 / 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/reachmail/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.