Brick
v1.0.0Brick integration. Manage data, records, and automate workflows. Use when the user wants to interact with Brick data.
⭐ 0· 60·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 ('Brick' integration) match the instructions: all actions use the Membrane CLI to connect to Brick and run actions or proxied API requests. There are no unrelated required env vars, binaries, or config paths requested.
Instruction Scope
SKILL.md stays on-topic: it describes installing and using @membranehq/cli, logging in, creating/listing connections, listing/running actions, and proxying requests to Brick. It does not instruct reading unrelated files, harvesting environment variables, or posting data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec in registry). It tells the user to install the Membrane CLI via `npm install -g @membranehq/cli` or use `npx`; asking users to run a global npm install is reasonable for a CLI but has the usual tradeoffs (global package install requires elevated permissions on some systems). No untrusted download URLs or archive extraction are present.
Credentials
The skill requests no environment variables or secrets. Authentication is handled by Membrane via browser-based login and connections, which is proportionate to a third-party API integration. The docs explicitly advise not to ask users for API keys or tokens locally.
Persistence & Privilege
The skill is not forced-always, and normal autonomous invocation is allowed (platform default). The skill does not request to modify other skills or system-wide settings. No elevated or persistent privileges are required by the skill itself.
Assessment
This skill appears consistent and focused on using the Membrane CLI to talk to Brick. Before installing/running: 1) verify you trust Membrane (https://getmembrane.com) because auth and requests go through their service; 2) prefer using `npx` or a scoped install rather than a global `npm install -g` if you want to avoid system-wide installs; 3) review the OAuth/connection scopes when you create a Brick connection so you understand what access you grant; 4) run commands in a development or isolated shell if you are cautious; and 5) do not provide local API keys (the skill explicitly expects Membrane to manage credentials).Like a lobster shell, security has layers — review code before you run it.
latestvk97fert6xc9dvz0s1dkj126jqn84bd87
License
MIT-0
Free to use, modify, and redistribute. No attribution required.