Postmark
v1.0.2Postmark integration. Manage Emails, Templates, Servers, Signatures, Domains, MessageStreams. Use when the user wants to interact with Postmark data.
⭐ 0· 233·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description state a Postmark integration and all runtime instructions are about using the Membrane CLI to connect to and operate on Postmark. Nothing requests unrelated cloud credentials or unrelated system access.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, creating connections, listing/running actions, and proxying to Postmark. Important privacy/security note: the skill explicitly instructs use of Membrane's proxy and action layer, which means API requests and email content are routed through Membrane's servers — this is expected for the described workflow but is a relevant data-exposure consideration.
Install Mechanism
There is no registry install spec; the SKILL.md tells the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal way to get the CLI but does execute third-party code on the machine — verify the @membranehq/cli package on npm/GitHub before installing.
Credentials
The skill does not request environment variables, secrets, or config paths. It delegates credential management to Membrane rather than asking for API keys, which is coherent with its guidance.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or agent-wide settings, and is user-invocable. Autonomous invocation remains possible (platform default) but this skill does not request additional persistent privileges.
Assessment
This skill is coherent for managing Postmark via the Membrane platform, but before installing or following the SKILL.md: (1) Verify the @membranehq/cli npm package and its publisher (npm page, GitHub repo, recent release history). (2) Understand that using Membrane's actions/proxy means email metadata and potentially full message bodies will transit Membrane's servers — evaluate whether that is acceptable for your data sensitivity and compliance needs. (3) Prefer the described connection flow (browser-based auth) rather than sharing API keys. (4) If you cannot or will not trust a third-party proxy for sensitive emails, use Postmark's API/official SDKs directly instead.Like a lobster shell, security has layers — review code before you run it.
latestvk979kcj4hd6x793twxcxy7093x842d7n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.