B Link
v1.0.0B.Link integration. Manage data, records, and automate workflows. Use when the user wants to interact with B.Link data.
⭐ 0· 64·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
Name/description, declared needs (network + Membrane account), and runtime commands all focus on using the Membrane CLI to interact with B.Link. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md limits activity to installing/using the Membrane CLI, creating/looking up connections, running actions, and proxying API requests through Membrane. It does not instruct reading unrelated files, requesting local secrets, or exfiltrating data to unexpected endpoints.
Install Mechanism
There is no formal install spec in the registry; the doc tells users to run `npm install -g @membranehq/cli`. That is a reasonable, common install pattern but installing global npm packages requires elevated permissions and trusts the npm package source—worth verifying the package and its upstream repository before installing.
Credentials
The skill declares no environment variables, no keys, and relies on Membrane to manage auth. This matches the stated approach of creating connections and letting Membrane handle credentials server-side.
Persistence & Privilege
The skill is not forced-always, does not request system-wide config changes, and does not require elevated persistent privileges. Autonomous invocation is permitted by default but not combined with other concerning factors here.
Assessment
This skill is internally consistent for a B.Link integration that uses Membrane. Before installing or following the SKILL.md steps: (1) verify the authenticity of the npm package `@membranehq/cli` (check its npm page and GitHub repo for maintainer and recent activity) because global npm installs run code on your machine; (2) review Membrane's privacy/security docs and the permissions the connection will grant to ensure it only has the access you intend to B.Link data; (3) prefer running CLI commands in a controlled environment (not a sensitive production machine) when doing first-time setup; and (4) if you need higher assurance, inspect the Membrane CLI source code or use a container/VM for installation to limit blast radius.Like a lobster shell, security has layers — review code before you run it.
latestvk9768e5hjjaz94rqk1pene11ah84bb7e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.