Magicbell
v1.0.2MagicBell integration. Manage data, records, and automate workflows. Use when the user wants to interact with MagicBell data.
⭐ 0· 94·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 SKILL.md describes a MagicBell integration implemented by using the Membrane platform/CLI. Asking the agent to install and use the Membrane CLI to connect and proxy MagicBell requests is consistent with the skill's stated purpose.
Instruction Scope
Instructions only cover installing the Membrane CLI, logging in, creating a connection, listing actions, running actions, and proxying requests through Membrane — all within the integration scope. Important: proxying sends API calls and payloads to Membrane's servers and places credentials/refresh handling on Membrane; the file does not ask the agent to read unrelated local files or secrets.
Install Mechanism
No formal install spec is included in the registry, but SKILL.md recommends running 'npm install -g @membranehq/cli'. This is a normal way to obtain the CLI (npm registry). Because the skill is instruction-only, nothing is installed automatically by the skill, but users following the instructions will install a third-party npm package — moderate trust/risk that should be evaluated by the user.
Credentials
The skill declares no required environment variables or secrets and explicitly advises not to ask users for API keys, relying on Membrane to manage credentials. That is proportionate to the stated functionality.
Persistence & Privilege
The skill does not request always-on presence or elevated platform privileges. It is user-invocable and permits autonomous invocation by default (platform normal) but does not add persistent system-wide changes itself.
Assessment
This skill is coherent: it tells you to install and use the Membrane CLI to manage MagicBell via Membrane's proxy. Before installing/running anything: (1) Understand that API requests, payloads, and credential handling will go through Membrane's servers — review Membrane's security, privacy, and data retention policies and the scopes granted when you create the connection. (2) When installing the CLI, prefer to verify the npm package (@membranehq/cli) and consider installing in a virtualenv/container rather than globally (-g) on shared machines. (3) In headless or shared environments be careful with the one-time login codes/URLs that complete authentication. (4) If you need to avoid a third-party proxy for privacy/regulatory reasons, do not use this skill and instead integrate directly with MagicBell using your own vetted tooling.Like a lobster shell, security has layers — review code before you run it.
latestvk97a29frfgb593g4krn38tgxgn843dxh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.