Branch
v1.0.2Branch integration. Manage data, records, and automate workflows. Use when the user wants to interact with Branch data.
⭐ 0· 100·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 claims to integrate with Branch and all runtime instructions use the Membrane CLI to discover connections, run actions, and proxy API requests to Branch. Required network access and a Membrane account are consistent with that purpose; no unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI (login, connect, action list/run, request proxy). It doesn't ask the agent to read local files, harvest unrelated env vars, or send data to unexpected endpoints; proxied requests go through Membrane as documented.
Install Mechanism
There is no formal install spec (instruction-only). It recommends installing @membranehq/cli via `npm install -g`, which is a public npm package — a typical approach but carries the usual npm-global risks. Recommend verifying the package source (npm/GitHub) or using `npx`/local install to avoid a global install if you prefer.
Credentials
The skill declares no required environment variables or local credentials. It relies on Membrane to handle auth server-side and explicitly advises not to ask users for API keys, which is proportionate for a connector-style integration.
Persistence & Privilege
always is false and there are no install steps that modify other skills or system-wide configs. The skill allows autonomous invocation (platform default), which is expected for operational skills and is not by itself a red flag here.
Assessment
This skill appears coherent and limited to using the Membrane CLI to talk to Branch. Before installing: (1) verify the @membranehq/cli package on npm/GitHub to ensure it’s the official CLI, or use `npx` to avoid a global install; (2) be prepared for a browser-based login flow (or headless completion flow) since Membrane handles auth; (3) understand that Membrane will hold/access Branch credentials on your behalf — only grant the connection scopes you need; (4) if you have strict policies about installed tooling, consider running the CLI in an isolated environment (container) or using a temporary/ephemeral approach.Like a lobster shell, security has layers — review code before you run it.
latestvk97ffe3s0w9y8rrah70rexd34d84267k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.