Databox
v1.0.0Databox integration. Manage data, records, and automate workflows. Use when the user wants to interact with Databox data.
⭐ 0· 54·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 (Databox integration) matches the instructions: all runtime steps are about installing and using the Membrane CLI to connect to Databox. No unrelated credentials, binaries, or system paths are requested.
Instruction Scope
SKILL.md restricts actions to installing/using the Membrane CLI, creating connections, listing actions, running actions, and optionally proxying requests to Databox via Membrane. It does allow raw proxied API calls (membrane request CONNECTION_ID /path) which gives broad ability to call arbitrary Databox endpoints — expected for an integration but something to be conscious of.
Install Mechanism
Install instructions use npm -g @membranehq/cli (public npm package). This is a standard approach but does install a global CLI; moderate trust in the upstream package and publisher is required. There is no download from untrusted URLs or archived extract steps.
Credentials
No local environment variables or secrets are requested. The skill relies on the Membrane service to hold and refresh Databox credentials server-side — this is proportionate but means the user delegates access to a third party (Membrane).
Persistence & Privilege
Skill is instruction-only, has no install spec in the registry, and does not request always:true or modification of other skills. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill is just documentation for using the Membrane CLI to access Databox and is internally consistent. Before installing: (1) confirm the @membranehq/cli package and publisher on npm/GitHub to ensure you trust the maintainer; (2) prefer npx or a local install instead of global npm installs on shared machines; (3) understand that using Membrane delegates Databox credentials and API access to Membrane's service (review their privacy/security policy); and (4) when running raw proxied requests, be careful which endpoints and data you access or expose.Like a lobster shell, security has layers — review code before you run it.
latestvk970nq8896c2g8a2psqxzfp3k984dy4q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.