Copperx
v1.0.2Copperx integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Copperx data.
⭐ 0· 97·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 say 'Copperx integration' and the instructions exclusively describe using the Membrane CLI to connect to Copperx, list actions, run actions, and proxy API requests. No unrelated env vars, binaries, or config paths are requested, so required capabilities align with the stated purpose.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating a connection, listing/running actions, and proxying requests. Note: the proxy feature lets you send arbitrary requests to Copperx APIs via Membrane (broad access to Copperx data once a connection is authorized), which is expected for this integration but worth being aware of.
Install Mechanism
The skill instructs users to run 'npm install -g @membranehq/cli' (global npm install). This is a reasonable install path for a CLI but is a moderate-risk operation because it installs third-party code system-wide — verify the package name and source before installing, and avoid global installs on shared or sensitive hosts.
Credentials
No environment variables or credentials are declared by the skill. That is coherent because Membrane CLI handles authentication and stores tokens locally; the skill does not request unrelated secrets. Be aware that Membrane will manage Copperx credentials and refresh tokens in its own config/store.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide config changes. It does not ask to modify other skills or global agent settings. Default autonomous invocation is allowed by platform policy but does not combine with other red flags here.
Assessment
This is an instruction-only skill that expects you to install the Membrane CLI and authenticate to Copperx via Membrane. Before installing: (1) verify the npm package '@membranehq/cli' is legitimate (check the npmjs.org page and the project's GitHub repo), (2) install the CLI only on a machine you control (avoid global installs on shared/CI hosts), (3) review where Membrane stores credentials on your system (so you know where tokens are kept) and consider using least-privilege Copperx credentials or a dedicated account, and (4) remember the 'membrane request' proxy can access any Copperx API endpoint once authorized — only authorize connectors you trust. Because this skill contains no embedded code and asks for no unrelated secrets, the primary risks are installing the external CLI and granting it access to Copperx data; those are expected for this integration.Like a lobster shell, security has layers — review code before you run it.
latestvk97b1g88abc5gs89bt2sm8q7zd842rtx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.