Criteo
v1.0.2Criteo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Criteo data.
⭐ 0· 120·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 (Criteo integration) matches the instructions: all runtime steps use the Membrane CLI to connect to Criteo, discover actions, run actions, or proxy requests. No unrelated services, binaries, or credentials are requested.
Instruction Scope
SKILL.md contains concrete CLI steps (install membrane CLI, login, create connections, list actions, run actions, proxy requests). It does not instruct the agent to read arbitrary files, access unrelated env vars, or exfiltrate data. Authentication is handled via browser-based Membrane login flow as described.
Install Mechanism
There is no packaged install spec in the registry (instruction-only). The doc recommends installing @membranehq/cli via npm -g, which is a standard public registry install. This is generally reasonable but requires trusting the npm package/publisher and that global installs may need elevated privileges.
Credentials
The skill declares no required env vars or credentials and explicitly advises not to ask the user for API keys. All credential handling is delegated to Membrane, so requested permissions are proportionate to the stated purpose.
Persistence & Privilege
always is false and the skill is user-invokable. There is no indication the skill modifies other skills or requires persistent system-wide changes beyond installing the Membrane CLI at the user's discretion.
Assessment
This skill is instruction-only and uses the Membrane CLI to interact with Criteo. Before installing/invoking: (1) verify the @membranehq/cli package on npm (publisher, version, trustworthiness) because the instructions recommend npm install -g; (2) expect a browser-based login flow that delegates credential handling to Membrane (you will not need to paste Criteo API keys into the skill); (3) global npm installs may require admin rights—consider using a node version manager or a scoped/local install if you prefer; (4) confirm the Membrane service (getmembrane.com) and the CLI are acceptable to your security policy since credentials are managed server-side by Membrane. Otherwise, the skill's requested actions and instructions are coherent with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk97960h15r1aw38ghp2csjcmrd8429tb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.