Privacera
v1.0.2Privacera integration. Manage data, records, and automate workflows. Use when the user wants to interact with Privacera data.
⭐ 0· 88·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 name/description (Privacera integration) match the SKILL.md: it documents using the Membrane CLI to manage Privacera resources and discover actions. Asking users to have a Membrane account and network access is consistent with that purpose.
Instruction Scope
The SKILL.md stays focused on interacting with Privacera via the Membrane CLI (installing the CLI, logging in, listing/connecting, running actions, proxying requests). It does require running CLI commands and completing browser-based auth flows; it does not instruct reading unrelated local files or exfiltrating data. Note: many commands assume the environment can run npm and open a browser or accept manual headless steps.
Install Mechanism
There is no platform-managed install spec; the README recommends installing an external npm package (npm install -g @membranehq/cli). Installing a global npm package is a moderate supply-chain risk but is expected here because the skill relies on that CLI. The skill itself does not bundle or download code.
Credentials
The skill declares no required env vars or credentials and relies on Membrane's auth flows. That is proportionate: authentication occurs via the Membrane CLI/browser connector rather than asking for unrelated secrets in the skill metadata.
Persistence & Privilege
The skill is instruction-only (no always: true) and does not request persistent platform privileges. Installing the CLI would write files to the host if you follow the instructions, but the skill metadata does not force persistent presence or modify other skills.
Assessment
This skill is coherent: it’s a how-to for using the Membrane CLI to work with Privacera. Before installing or running it, consider: (1) the SKILL.md asks you to install a global npm package (@membranehq/cli) — ensure you trust that package and your environment's supply chain policies; (2) you will need a Membrane account and to complete browser-based auth flows (or headless code completion steps) which may issue tokens stored locally by the CLI; (3) the skill does not ask for Privacera credentials directly, but the connector you create will grant whatever access you approve — follow least-privilege practices for that connector; (4) if you do not want agents to execute CLI commands or open auth flows on your behalf, avoid invoking this skill or run the commands manually in a controlled environment.Like a lobster shell, security has layers — review code before you run it.
latestvk973qez2agtedqavj43ja5vnpn843xac
License
MIT-0
Free to use, modify, and redistribute. No attribution required.