Backblaze
v1.0.2Backblaze integration. Manage data, records, and automate workflows. Use when the user wants to interact with Backblaze data.
⭐ 0· 76·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 (Backblaze integration) matches the instructions: all actions are performed via the Membrane CLI and/or Membrane's proxy to Backblaze. There are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
The SKILL.md stays on task (install Membrane CLI, authenticate via browser, create a Backblaze connection, run actions or proxy requests). It explicitly tells the agent to route API calls through Membrane's proxy; this is coherent with the stated purpose but means API requests and payloads will traverse Membrane's service—users should expect that networked data and request bodies go to Membrane.
Install Mechanism
This is an instruction-only skill (no install spec in registry), but the instructions require installing @membranehq/cli via npm (global install recommended). Installing a global npm CLI is a normal but non-zero risk action (running third-party code on the host); the package is namespaced to @membranehq which is consistent with the service referenced.
Credentials
No environment variables, primary credential, or config paths are requested. The SKILL.md explicitly advises not to ask users for Backblaze API keys and to let Membrane handle auth server-side—this aligns with the absence of local secret requirements.
Persistence & Privilege
Registry flags show no forced persistence (always: false) and the instructions do not request modifying other skills or system-wide agent settings. The skill does require the user to install and log into a CLI, but that is scoped to the user's environment.
Assessment
This skill appears to do what it describes: it uses the Membrane CLI to connect to Backblaze and run actions. Before installing or using it, consider: (1) you will install and run a third‑party npm CLI (@membranehq/cli) on your machine—review the package and run it in a controlled environment if you are cautious; (2) API calls and request payloads will be proxied through Membrane's servers, so review Membrane's privacy/security docs and the permissions you grant during browser-based authentication; (3) do not supply Backblaze API keys directly to the skill—use the connection flow as documented; (4) if you need stricter isolation, consider running the CLI in a container or test account first.Like a lobster shell, security has layers — review code before you run it.
latestvk976jgpwkmzbw7p8y8cp467gk1843313
License
MIT-0
Free to use, modify, and redistribute. No attribution required.