Privacy Dynamics
v1.0.0Privacy Dynamics integration. Manage data, records, and automate workflows. Use when the user wants to interact with Privacy Dynamics data.
⭐ 0· 109·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
medium confidencePurpose & Capability
The name/description say "Privacy Dynamics integration" and every runtime instruction uses the Membrane CLI to discover connectors, create connections, run actions, or proxy API calls to Privacy Dynamics. There are no unrelated credentials, binaries, or paths requested — the declared purpose matches the required operations.
Instruction Scope
All instructions are limited to installing and using the @membranehq/cli to authenticate and run proxied requests against Privacy Dynamics. Important: the guidance relies on Membrane's proxy and auth handling, which means requests and possibly sensitive data will transit Membrane's service and credentials are managed server-side. This is expected for a proxy-based integration but is a privacy/security consideration the user should accept explicitly.
Install Mechanism
The skill is instruction-only (no install spec in the registry) but tells users to run `npm install -g @membranehq/cli` or use `npx`. Using the official npm package name is reasonable for this purpose, but global npm installs should be vetted by the user (package publisher, package contents, and permissions).
Credentials
The skill requests no environment variables or local secrets and explicitly advises not to ask users for API keys. This aligns with the stated approach of using Membrane to manage credentials server-side.
Persistence & Privilege
The skill is not force-enabled (always: false) and does not request persistent system-wide configuration or access to other skills' settings. Autonomous invocation is allowed by platform default; there are no additional privilege requests from the skill itself.
Assessment
This skill is internally consistent: it tells the agent to install and use the Membrane CLI to connect to Privacy Dynamics and proxy API requests. Before installing or using it, verify the Membrane service and npm package (@membranehq/cli): check the publisher, GitHub repo, and privacy/security docs; prefer using `npx` for one-off runs instead of a global install if you want to limit system impact; be aware that data and authentication will be handled by Membrane (requests and possibly sensitive fields will flow through their servers), so do not send highly sensitive data until you are comfortable with their controls and retention policies; and consider testing with a non‑production/test tenant first. If you need higher assurance, ask the skill author for the exact package version they expect and the upstream repository/source for the CLI binary so you can review it.Like a lobster shell, security has layers — review code before you run it.
latestvk979821sx8ewsq3hmht71jgacn84gdm8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.