Acumbamail
v1.0.2Acumbamail integration. Manage data, records, and automate workflows. Use when the user wants to interact with Acumbamail data.
⭐ 0· 129·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
high confidencePurpose & Capability
The name/description (Acumbamail integration) matches the instructions: all runtime steps use the Membrane CLI to discover, connect, and proxy requests to Acumbamail. There are no unrelated env vars, binaries, or config paths requested.
Instruction Scope
SKILL.md instructs installing and using the @membranehq/cli, performing login via browser, creating connections, listing and running actions, and proxying API requests through Membrane. It does not instruct reading arbitrary local files or exfiltrating data, but it does instruct the user/agent to delegate auth and API traffic to Membrane (i.e., the service will hold and use Acumbamail credentials).
Install Mechanism
There is no automated install spec in the skill bundle (lowest risk), but the docs recommend a manual global npm install of @membranehq/cli. Installing a global npm package is a normal but nontrivial action: verify the package and publisher before running it.
Credentials
The skill declares no required env vars or local credentials (good). However, it depends on a Membrane account and creates connections that cause Membrane to hold and use Acumbamail tokens on your behalf — this requires trusting the Membrane service and its access scopes.
Persistence & Privilege
The skill does not demand always:true, does not modify other skills, and offers no install that would persist autonomously. It is user-invocable and can be used by agents, which is the platform default and expected.
Assessment
This skill is coherent with its stated purpose, but before using it you should: (1) confirm you trust Membrane (getmembrane.com) because the service will hold and use Acumbamail auth tokens when you create a connection; (2) verify the @membranehq/cli package on npm and the repository (avoid installing unknown global packages); (3) review the OAuth/scopes presented during membrane login and grant least privilege (or use a dedicated Acumbamail account); (4) do not provide Acumbamail API keys manually to the agent — follow the connection flow described; and (5) if you need higher assurance, inspect the Membrane CLI code/repo and the Membrane privacy/security docs before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk977fw9g33g12gyerxnxeaz39n8433yt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.