Letterdrop
v1.0.0Letterdrop integration. Manage Organizations. Use when the user wants to interact with Letterdrop data.
⭐ 0· 58·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill's name and description (Letterdrop integration) align with the instructions: it uses Membrane as a connector/proxy to interact with Letterdrop. No unrelated env vars, binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs the agent/operator to run npx @membranehq/cli commands to log in, create connections, list actions, run actions, and proxy arbitrary API paths. These instructions stay within the stated Letterdrop integration purpose, but the proxy feature can forward arbitrary endpoints and payloads through Membrane (a third party), and credentials will be persisted to ~/.membrane/credentials.json.
Install Mechanism
There is no packaged install spec, but runtime instructions use npx @membranehq/cli@latest which dynamically fetches and executes code from the npm registry. Using the @latest tag means behavior can change over time; dynamic fetching executes remote code without a pinned/verifiable release.
Credentials
The skill declares no required environment variables or credentials. It explicitly defers auth to Membrane (recommended) instead of asking users for API keys, which is proportionate. Be aware credentials are stored locally at ~/.membrane/credentials.json after login and Membrane operates as the authentication proxy.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide settings, and is user-invocable/autonomous-invocation defaults are normal. It does not request elevated persistence or cross-skill access.
Assessment
This skill appears to do what it claims (connect to Letterdrop) using the Membrane CLI, but there are two things to consider before installing:
- Remote code execution: The runtime instructions rely on npx @membranehq/cli@latest, which will download and run code from the npm registry each time. Prefer a pinned version (not @latest) or inspect the package source before running to reduce supply-chain risk.
- Third-party proxying and privacy: Requests can be proxied through Membrane (including full URLs and bodies). That means Membrane will see request contents and handle auth — review Membrane's privacy/security and whether you trust it to handle your Letterdrop data and credentials. Credentials are stored locally at ~/.membrane/credentials.json after login; treat that file as sensitive.
Additional practical checks: verify the @membranehq package and its publisher, review Membrane docs and privacy policy, and avoid pasting sensitive data into proxied requests unless you trust the service. If you require higher assurance, ask the skill author for a pinned CLI version or a hosted integration with audited code.Like a lobster shell, security has layers — review code before you run it.
latestvk97djgk9p2j1m2a0kykewgd6h184apqp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.