Name: smartrmail
Rating: 55.2 (1 reviews)
Author: membranedev

smartrmail

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

Quality

62%

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/smartrmail/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 delivers concrete, executable Membrane CLI guidance with a well-sequenced connection workflow and clear state-based validation, but it carries some marketing-flavored padding and a redundant actions section that could be trimmed.

Suggestions

Trim the marketing-style intro paragraph and filler phrases like "so you can focus on the integration logic rather than auth plumbing" — Claude does not need SmartrMail's value proposition.

Remove or merge the redundant "Popular actions" section, which repeats the `action list` command already shown under "Searching for actions."

Add a brief validation or confirmation step before running potentially destructive actions (e.g., preview inputs or confirm with the user) to strengthen the workflow's safety.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the marketing-style intro paragraph ("helps online stores automate email campaigns… grow their email list and increase sales") and phrases like "so you can focus on the integration logic rather than auth plumbing," fitting the score-3 anchor.	3 / 5
Actionability	It provides mostly executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with a flags table, with only minor gaps from unfilled placeholders like CONNECTION_ID and QUERY, matching the score-4 anchor.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-check checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, with only minor gaps such as no validation before running potentially destructive actions, fitting score 4.	4 / 5
Progressive Disclosure	No bundle files exist and the content is well-organized into clearly headed sections with no nested references, but the redundant "Popular actions" section and inline clientAction detail leave minor organization gaps, placing it at score 4.	4 / 5
	Total	15 / 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 correctly uses third-person voice and includes both a what and a when clause, but its action list is generic and its trigger terms lean on the product name rather than natural email-marketing phrasings.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete SmartrMail actions such as "create email campaigns, manage subscribers, and recover abandoned carts."

Add natural trigger terms users would actually say — "email marketing," "newsletters," "email campaigns," "abandoned cart recovery" — so the skill triggers on common phrasings rather than only "SmartrMail data."

Dimension	Reasoning	Score
Specificity	The description names the domain (SmartrMail) but its actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete email-marketing actions, matching the score-2 anchor.	2 / 5
Completeness	Both "what" (SmartrMail integration; manage data, records, automate workflows) and "when" ("Use when the user wants to interact with SmartrMail data") are present, though the trigger could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	It includes the relevant product-name keyword ("SmartrMail") in its trigger, but misses common natural variations users would say such as "email marketing," "campaigns," "newsletters," or "abandoned carts," fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product SmartrMail gives it a clear niche with minimal conflict risk, but the generic action phrasing could overlap with sibling Membrane integration skills, placing it at score 4 rather than 5.	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/smartrmail/SKILL.md
Commit: f484c82

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