Fireeye
v1.0.2FireEye integration. Manage data, records, and automate workflows. Use when the user wants to interact with FireEye data.
⭐ 0· 84·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 SKILL.md describes FireEye integration exclusively via the Membrane CLI and Membrane-managed connections. There are no unexpected environment variables, binaries, or config paths requested that don't belong to this purpose.
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI, logging in, creating/listing connections, running actions, and proxying API requests through Membrane. The instructions do not tell the agent to read unrelated files, export arbitrary local secrets, or call endpoints outside the Membrane/FireEye context.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells users to run `npm install -g @membranehq/cli` (or use npx). Installing an external npm CLI is a normal step for this integration, but npm packages can execute install hooks and modify the system. The skill itself does not embed or download code.
Credentials
The skill requests no environment variables or local credentials. It relies on Membrane to manage authentication server-side, which is appropriate for a connector and reduces local secret handling. The only proportional concern is that users must trust Membrane with FireEye access.
Persistence & Privilege
The skill does not request always: true or any special persistent privileges, and it does not instruct modifications to other skills or system-wide settings. Model invocation is allowed (platform default) but not elevated here.
Assessment
This skill appears coherent: it works through the Membrane CLI and does not ask for unrelated secrets. Before installing: (1) Confirm you trust Membrane/getmembrane.com and the @membranehq npm package (review the npm package page and GitHub repo), because installing a global npm CLI will run code on your machine. (2) Be aware you must create/login to a Membrane account and grant it access to your FireEye tenant — review Membrane's privacy/permissions and the connector details. (3) If you prefer safer testing, install the CLI in an isolated environment/container or inspect the package source first. If you are uncomfortable granting a third-party proxy account broad access to FireEye data, do not proceed.Like a lobster shell, security has layers — review code before you run it.
latestvk976prkgzcjcp5x7108da9vzyx843t5g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.