Caseblocks
v1.0.0Caseblocks integration. Manage data, records, and automate workflows. Use when the user wants to interact with Caseblocks data.
⭐ 0· 54·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 match the runtime instructions: the SKILL.md describes using Membrane CLI to connect to Caseblocks, discover actions, run them, and proxy API requests — all coherent with a Caseblocks integration.
Instruction Scope
Instructions only tell the agent to install and use the Membrane CLI, run connector/action/connection commands, and proxy requests to Caseblocks via Membrane. There are no instructions to read arbitrary local files, request unrelated credentials, or send data to unexpected endpoints.
Install Mechanism
Installation is via a public npm package (@membranehq/cli) called by the user (npm install -g). This is expected for a CLI integration but carries the usual supply-chain considerations of installing global npm packages — user should trust the package publisher.
Credentials
The skill requests no environment variables or credentials. The SKILL.md explicitly instructs using Membrane-managed connections (server-side auth) instead of asking for API keys, which is proportionate to the described functionality.
Persistence & Privilege
No 'always' privilege requested and the skill is user-invocable. It does not request to modify other skills or system-wide settings. Normal autonomous invocation is permitted by platform defaults.
Assessment
This skill is instruction-only and leverages the Membrane CLI to access Caseblocks, which is consistent with its description. Before installing: (1) confirm you trust the @membranehq npm package and its publisher (global npm installs affect your system PATH); (2) expect browser-based authentication flows that grant Membrane access to Caseblocks on your behalf (server-side tokens live with Membrane); and (3) avoid running in an untrusted/headless environment without understanding how the login completion code is handled. If you need stricter control, review Membrane's privacy/security docs and the @membranehq/cli package source before installation.Like a lobster shell, security has layers — review code before you run it.
latestvk97bnbdadjsp6kmx5496xhy8zh84cc7t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.