Lane
v1.0.2Lane integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lane data.
⭐ 0· 72·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
Name/description map to the instructions: the SKILL.md consistently describes using the Membrane CLI to connect to a Lane connector, list actions, run them, and proxy API requests. Required capabilities (network, Membrane account, Membrane CLI) are appropriate for a Lane integration.
Instruction Scope
Runtime instructions only describe installing/using the Membrane CLI, logging in, creating/listing connections, running actions, and proxying requests to Lane. There are no instructions to read unrelated files, exfiltrate local data, or fetch unrelated credentials. The guidance to avoid asking users for API keys and to let Membrane manage credentials is explicit.
Install Mechanism
The skill is instruction-only (no install spec in registry). It tells users to install @membranehq/cli via npm (-g) or to use npx. Installing a third-party CLI from npm is expected for this integration but does execute third-party code on the machine — recommend using npx or reviewing the package/source before a global install.
Credentials
The skill declares no required env vars, no config paths, and the instructions explicitly rely on Membrane for auth rather than local secrets. This is proportional to the described functionality.
Persistence & Privilege
The skill is not forced-always and does not request system-level persistence. It's an instruction-only skill that triggers CLI actions at runtime; nothing in the SKILL.md attempts to modify other skills or agent-wide settings.
Assessment
This skill looks consistent: it relies on the official Membrane CLI to talk to Lane and doesn't ask for unrelated secrets. Before installing/using it: (1) Confirm @membranehq/cli is the expected package and review its npm/github page; (2) prefer npx to avoid global installs if you don't want new system binaries; (3) be aware the login flow opens a browser and grants Membrane access to your Lane account — only proceed if you trust getmembrane.com and the Membrane service; (4) review the permissions the connector requests when you authenticate; and (5) if you need tighter control, consider creating a least-privilege account or sandbox environment for initial testing.Like a lobster shell, security has layers — review code before you run it.
latestvk973b0fdsxf7ad2jgqn9s6pmvh8436dg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.