Density
v1.0.0Density integration. Manage data, records, and automate workflows. Use when the user wants to interact with Density data.
⭐ 0· 25·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
medium confidencePurpose & Capability
The name/description (Density integration) aligns with the instructions (using Membrane to connect to Density and run actions). Minor mismatch: the SKILL.md instructs installing the Membrane CLI (npm package), but the skill registry metadata declares no required binaries — the runtime will effectively require npm/node and the membrane CLI to be present.
Instruction Scope
SKILL.md only instructs operations related to connecting to Density via Membrane (login, connect, action list/run, proxy requests). It does not ask the agent to read unrelated files, env vars, or exfiltrate data to unexpected endpoints. Proxying requests to Density via Membrane is expected behavior for this integration.
Install Mechanism
There is no formal install spec in the registry, but the instructions require installing @membranehq/cli via npm (global install or npx). Installing a package from the public npm registry is reasonable for this use case, but it implies needing npm/node and will write software to disk — the skill did not declare these binaries upfront.
Credentials
The skill declares no required environment variables or credentials and explicitly instructs users to let Membrane handle credentials. This is proportionate. One privacy/ops note: using Membrane means requests and credentials are handled by Membrane's service (getmembrane.com), so trust in that provider is required.
Persistence & Privilege
The skill is user-invocable and not always-enabled; it does not request elevated platform privileges or modify other skills. Autonomous invocation is allowed (platform default) and not in itself a concern here.
Assessment
This skill appears to be what it says: a wrapper that teaches the agent to use the Membrane CLI to interact with Density. Before installing or using it, confirm you are comfortable installing a global npm package (@membranehq/cli) and that your environment has npm/node available. Understand that Membrane (getmembrane.com) will broker authentication and proxy API requests — that provider will see proxied requests and potentially sensitive occupancy data, so verify the service and scopes you authorize. Also prefer using the connection flow (browser auth) rather than handing out API keys locally. If you need higher assurance, check the @membranehq/cli package on npm/GitHub and validate the connector IDs and permissions it requests.Like a lobster shell, security has layers — review code before you run it.
latestvk970zbd060k83ejheberwrt06n846vgn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.