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

Blog Docs Log in Get started

letterdrop

Letterdrop integration. Manage Organizations. Use when the user wants to interact with Letterdrop 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/letterdrop/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, actionable Membrane CLI wrapper with concrete commands throughout. Its weak spots are marketing-fluff padding in the intro, an empty 'Popular actions' section, and implicit rather than explicit validation checkpoints in the workflow.

Suggestions

Remove the marketing description of Letterdrop ('streamline their workflows and improve content performance') and the filler line 'Use action names and parameters as needed'.

Populate 'Popular actions' with the actual named actions (Newsletter, Subscriber, Email, Analytics) or remove the heading if discovery is the intended path.

Add explicit verification checkpoints (e.g., 'Confirm the connection appears in `connection list` before running actions') to the workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI command listings, but the marketing-fluff intro ('streamline their workflows and improve content performance') and the filler line 'Use action names and parameters as needed' could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready `npx @membranehq/cli@latest` commands with flags and JSON examples cover the common cases; the gap is the 'Popular actions' section that promises actions but lists none.	4 / 5
Workflow Clarity	A clear setup → connect → discover → run sequence is present, but validation checkpoints are only implicit (e.g., no step to verify a connection succeeded before running actions).	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections in a single file with no nested references; structure is good though the file exceeds the 50-line simple-skill threshold.	4 / 5
	Total	14 / 20 Passed

Description

62%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 includes a 'Use when' trigger and names a specific product, giving it reasonable distinctiveness and completeness. Its main weakness is a vague, slightly inaccurate 'what' clause ('Manage Organizations') that under-specifies the skill's real capabilities.

Suggestions

Replace 'Manage Organizations' with the concrete capabilities the skill actually exposes (e.g., 'Manage newsletters, subscribers, emails, and analytics').

Add natural trigger synonyms users might say, such as 'newsletter', 'subscriber', or 'Letterdrop campaigns'.

Ensure the 'what' clause matches the entities listed in the body (Newsletter, Subscriber, Email, Analytics) to avoid misleading Claude.

Dimension	Reasoning	Score
Specificity	The description names the domain (Letterdrop) and one action ('Manage Organizations'), but the action is generic and does not match the body's actual capabilities (Newsletter, Subscriber, Email, Analytics).	3 / 5
Completeness	Both a 'what' ('Manage Organizations') and an explicit 'when' ('Use when the user wants to interact with Letterdrop data') are present, though the 'what' side is thin.	4 / 5
Trigger Term Quality	'interact with Letterdrop data' is a relevant trigger phrase, but no synonyms, entity names, or common user variations are included.	3 / 5
Distinctiveness Conflict Risk	Letterdrop is a named SaaS product giving it a clear niche, but the sparse description leaves minor overlap risk with other marketing/content skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/letterdrop/SKILL.md
Commit: f484c82

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