Cyberimpact
v1.0.2Cyberimpact integration. Manage Contacts, Campaigns, Forms. Use when the user wants to interact with Cyberimpact data.
⭐ 0· 128·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
Name/description: Cyberimpact integration. What it actually requires: network access and the Membrane CLI, and a Membrane account. These are coherent and expected for a 3rd-party API integration proxying requests to Cyberimpact.
Instruction Scope
SKILL.md instructs installing and using the Membrane CLI, logging in via browser, creating/using connections, running predefined actions, and proxying arbitrary API requests through Membrane. All of these stay within the stated integration purpose. Note: the instructions will open a browser for auth and rely on Membrane to store/refresh credentials locally — the doc does not describe where credentials are persisted or their scopes.
Install Mechanism
No bundled install spec in the registry, but SKILL.md tells users to install @membranehq/cli via npm (npm install -g). That's a standard mechanism for CLI tools and appropriate for this purpose. It's a moderate-risk install because it pulls a package from npm, but it is proportionate and expected for a CLI-based integration.
Credentials
The skill declares no required environment variables or credentials. Runtime instructions require a Membrane account (via interactive CLI auth) and a Cyberimpact connection created through Membrane. No unrelated secrets or system credentials are requested.
Persistence & Privilege
Skill is instruction-only, always:false, and does not request persistent system-wide privileges. However, the Membrane CLI will persist authentication tokens/config locally as part of normal operation; the SKILL.md does not explicitly document where or how those tokens are stored or their lifetime. Autonomous invocation is allowed by platform default (not flagged by itself).
Assessment
This skill appears coherent: it uses the Membrane CLI to access Cyberimpact via a Membrane-managed connection. Before installing and using it: (1) verify you trust the @membranehq/cli npm package and its publisher (review the package on npm/github); (2) be aware the CLI will open a browser for auth and will store tokens/config locally — review where the CLI persists credentials and what scopes it requests; (3) installing a global npm package modifies your system environment (npm -g); if you have restrictions on global installs, consider using a controlled environment; (4) Membrane's proxy can run arbitrary API requests to Cyberimpact, so only grant it access to accounts you intend to expose; and (5) if you need stricter guarantees, inspect the Membrane CLI source code/repo before installation and limit the agent's autonomy or review actions before they run.Like a lobster shell, security has layers — review code before you run it.
latestvk976tzaennpy6m0t0jvn0g95p1842ef4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.