Name: smtp2go
Rating: 58.4 (1 reviews)
Author: membranedev

smtp2go

SMTP2GO integration. Manage data, records, and automate workflows. Use when the user wants to interact with SMTP2GO 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/smtp2go/SKILL.md

Quality

Content

75%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 content is highly actionable, with copy-paste CLI commands and a well-sequenced connection workflow including state-based feedback loops. Its main weakness is the unnecessary marketing/background opening and the absence of a verification step after running actions.

Suggestions

Remove the opening "SMTP2GO is an email delivery service..." background paragraph and "so you can focus on the integration logic rather than auth plumbing"; Claude does not need SMTP2GO's marketing pitch.

Add a verification step after `membrane action run`, e.g. check the response `output`/error fields and retry on failure, to close the validation gap in the action workflow.

Consider moving the proxy flags table and "Best practices" into a separate reference file so SKILL.md stays a lean overview with one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command references, but the opening marketing paragraph ("SMTP2GO is an email delivery service that helps businesses... It's used by developers, marketers, and businesses of all sizes") and phrases like "so you can focus on the integration logic rather than auth plumbing" explain background Claude does not need, fitting the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, connection get --wait, action list, action run, request) plus a flag table, fully executable and covering the common workflow.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-retry feedback loop, but the action-running workflow lacks an explicit verify-success step, fitting the "clear sequence with most checkpoints present; minor validation gaps" anchor.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections (Overview, Working with SMTP2GO, Auth, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, but as a single >50-line file with inline reference-style content (proxy flag table, best practices) it has minor organization gaps rather than the ideal one-level-deep reference split.	4 / 5
	Total	16 / 20 Passed

Description

61%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 names the SMTP2GO niche and includes an explicit Use-when clause, but its action language is generic ("manage data, records") and omits the natural email-related trigger terms a user would actually say. It is distinct and complete enough to activate, just not specific.

Suggestions

Replace generic verbs with concrete SMTP2GO actions, e.g. "Send and track transactional email, manage suppression lists, domains, and templates."

Add natural trigger terms users say: "Use when the user wants to send email via SMTP2GO, check email stats, or manage suppression lists/domains."

Drop "Manage data, records" which is vague and not specific to SMTP2GO's email-delivery purpose.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the SMTP2GO domain but the actions are generic and not concrete to the email domain (no mention of sending email, suppression lists, or templates), matching the "actions minimal or generic" anchor rather than the 1-2 concrete actions at score 3.	2 / 5
Completeness	It states both a "what" ("SMTP2GO integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with SMTP2GO data"), but the trigger clause is generic rather than listing concrete trigger phrases, fitting the "has both what and when; when could be more specific" anchor.	4 / 5
Trigger Term Quality	The brand term "SMTP2GO" is present and "interact with SMTP2GO data" gives some trigger coverage, but common natural terms users would say ("email", "send email", "suppression list", "deliverability") are missing, matching the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SMTP2GO brand in both the capability and trigger clause gives it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	14 / 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/smtp2go/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.