Name: postmark
Rating: 60 (1 reviews)
Author: membranedev

postmark

Postmark integration. Manage Emails, Templates, Servers, Signatures, Domains, MessageStreams. Use when the user wants to interact with Postmark data.

Quality

70%

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/postmark/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.

A well-structured, actionable integration guide centered on concrete Membrane CLI commands. Its main weaknesses are a mild verbosity in the intro/promotional lines, a skeletal Overview section that under-matches the description, and a lack of validation steps around the destructive and batch operations it lists.

Suggestions

Add an explicit validation/verification checkpoint before destructive and batch actions (e.g., confirm the template name/ID before "Delete Template", and preview or confirm recipient count before "Send Batch Emails").

Trim concept-explanation and promotional padding (the "Postmark is a transactional email service..." intro and phrases like "so you can focus on the integration logic") since Claude already knows this.

Expand the skeletal "Postmark Overview" section so it reflects all entities named in the description (Emails, Templates, Servers, Signatures, Domains, MessageStreams), or remove it if the popular-actions table already conveys the scope.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-and-table content, but it opens by explaining what Postmark is ("Postmark is a transactional email service... password resets, welcome messages...") which Claude already knows, and includes promotional padding like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready CLI commands for the common path (install, login, connection ensure, action list, action run, request proxy) plus a concrete popular-actions table. It stays at 4 rather than 5 because the run examples use generic placeholders ("<actionId>", "--input '{\"key\": \"value\"}'") instead of a fully worked real example.	4 / 5
Workflow Clarity	The connection workflow is well sequenced with explicit state checks and a poll-again feedback loop, but the skill exposes destructive and batch operations ("Delete Template", "Send Batch Emails ... up to 500") whose "Running actions" section gives only the generic run command with no validation or verification step, capping this dimension at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Working with Postmark, Popular actions, Proxy, Best practices) with no bundle files to split out. It is at 4 rather than 5 because the "Postmark Overview" section is skeletal (only Email/Server/Signature, mismatching the description's fuller entity list) and the inline popular-actions reference could be signaled more clearly.	4 / 5
	Total	14 / 20 Passed

Description

78%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, brand-specific description that names concrete Postmark entities and includes an explicit "Use when..." trigger. Its main weakness is bundling all actions under the generic verb "Manage" and a slightly generic trigger clause rather than concrete triggering scenarios.

Suggestions

Replace the single verb "Manage" with a few enumerated actions (e.g., "Send emails, create and update templates, manage servers and signatures") to lift specificity.

Make the trigger clause more concrete, e.g., "Use when the user wants to send transactional emails, manage Postmark templates, or check send/bounce statistics."

Dimension	Reasoning	Score
Specificity	"Manage Emails, Templates, Servers, Signatures, Domains, MessageStreams" names six concrete managed entities, but bundles them under the single generic verb "Manage" rather than enumerating specific actions (send, create, delete). It is comprehensive in coverage but lists objects rather than distinct actions, landing just below a 5.	4 / 5
Completeness	It has a clear "what" (manage the six Postmark entities) and an explicit "when" clause ("Use when the user wants to interact with Postmark data"). The trigger is explicit and present so it clears the 3-cap, but the "when" is somewhat generic ("interact with Postmark data") rather than naming concrete triggering scenarios.	4 / 5
Trigger Term Quality	Natural terms users would say are present ("Postmark", "Emails", "Templates", "Domains") plus the trigger phrase "interact with Postmark data". Coverage is good but misses common variations a user might say like "transactional email" or "send email", keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	"Postmark integration" targets a specific named transactional email service, giving it a clear niche with distinct brand triggers and minimal overlap risk with other skills.	5 / 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/postmark/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.