Cognite
v1.0.2Cognite integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cognite data.
⭐ 0· 81·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 (Cognite integration) match the instructions: the SKILL.md documents using the Membrane CLI to connect to Cognite, list actions, run actions, and proxy API requests. Nothing in the manifest or instructions asks for unrelated cloud credentials, files, or system access.
Instruction Scope
Instructions are focused on installing/using the Membrane CLI, creating a connection, running actions, and proxying requests. This enables arbitrary Cognite API calls via the Membrane proxy (expected for a connector). The SKILL.md does not instruct reading local files or unrelated environment variables. Note: proxying allows broad access to Cognite data — which is coherent with the skill’s purpose but worth auditing in practice.
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing @membranehq/cli via npm (public registry). The recommendation is expected for this integration; no automated download-from-URL or hidden install is present.
Credentials
The skill declares no required env vars or credentials and explicitly instructs not to ask users for API keys, relying on Membrane to handle auth. That is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request always:true and does not modify agent/system configuration. It is user-invocable and allows normal model invocation (platform default).
Assessment
This skill is coherent: it instructs use of the Membrane CLI to connect to Cognite and run actions or proxy API calls. Before installing or using it, verify you trust Membrane (@membranehq) and the npm package owner, and review the package and its permissions if possible. Be aware that once a connection exists, commands (or an agent using this skill) can make arbitrary requests to your Cognite tenant via the Membrane proxy — restrict the connection's permissions/service accounts on the Cognite side, audit actions, and avoid posting connection IDs or any returned tokens publicly. In headless or automated environments you'll need to complete Membrane's login flow (URL + code). If you want stricter control, create a least-privilege service account in Cognite for this integration and review Membrane's privacy/security docs before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97ewr05x79h7rexkk5h2hgvy18428hf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.