Name: turbosmtp
Rating: 50.4 (1 reviews)
Author: membranedev

turbosmtp

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

Quality

55%

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

Quality

Content

61%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 a well-structured, largely actionable guide to driving TurboSMTP through the Membrane CLI, with clear connection-state handling. Its main weaknesses are some marketing/filler prose, a lack of validation around destructive actions, and no fully-worked end-to-end example.

Suggestions

Tighten the intro to a single factual line and remove 'Use action names and parameters as needed.' and the duplicated command in 'Popular actions'.

Add a validation/verification step for destructive actions (e.g. confirm a contact list's contents with 'Get Contacts from List' and require explicit user confirmation before 'Delete Contact List'/'Delete Sender').

Include one fully-realized example showing connection ensure -> action list -> action run with concrete values, so the placeholders become concrete.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the marketing-flavored intro ('helps businesses reliably send...avoid spam filters'), the filler line 'Use action names and parameters as needed.', and the 'Popular actions' section repeating an already-shown command add unnecessary tokens that could be trimmed.	3 / 5
Actionability	Provides many concrete, copy-pasteable commands (install, login, connection ensure, action run, request) plus a flags table, with only minor gaps such as unresolved placeholders (CONNECTION_ID, QUERY) and no fully-realized end-to-end example.	4 / 5
Workflow Clarity	Connection setup is well-sequenced with state-check feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the skill exposes destructive operations (Delete Contact List, Delete Sender) with no validation or verification steps, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized with clear section headers and no nested references; it is appropriately structured with only minor organization gaps (the inline action inventory could conceptually live separately), landing above the midpoint but short of the one-level-deep reference structure of a 5.	4 / 5
	Total	14 / 20 Passed

Description

48%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 TurboSMTP niche and includes an explicit Use-when trigger, but its capability language is generic Membrane boilerplate ('manage data, records, and automate workflows') rather than concrete email actions. It is distinguishable but lacks specificity and natural email-domain keywords.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions, e.g. 'Send transactional and marketing emails, manage contact lists and senders, and track email opens, clicks, and status.'

Expand the trigger clause with natural email terms: 'Use when the user wants to send or track TurboSMTP emails, or manage TurboSMTP contacts, lists, or senders.'

Confirm third-person voice is preserved (it is) and keep the description concise — the current length is fine once the boilerplate is made specific.

Dimension	Reasoning	Score
Specificity	Names the domain ('TurboSMTP integration') but the actions are generic boilerplate ('Manage data, records, and automate workflows') with no concrete operations like send email or manage contact lists, matching the 'names domain but actions minimal/generic' anchor rather than the 1-2 concrete actions of a 3.	2 / 5
Completeness	Both 'what' and an explicit 'when' ('Use when the user wants to interact with TurboSMTP data') are present, but the 'what' is templated and vague and the 'when' is generic, landing at the midpoint rather than the 4 which expects a more concrete when.	3 / 5
Trigger Term Quality	Includes the natural brand keyword 'TurboSMTP' in a Use-when clause, but misses common email-domain variations (send email, contact lists, senders), fitting 'some relevant keywords but missing common variations' better than the single-generic-keyword anchor 2.	3 / 5
Distinctiveness Conflict Risk	The specific brand 'TurboSMTP' carves a clear niche with minimal conflict risk, though the generic 'manage data, records, and automate workflows' tail could overlap with sibling Membrane integration skills, keeping it just below a 5.	4 / 5
	Total	12 / 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/turbosmtp/SKILL.md
Commit: f484c82

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