Dimdata

v1.0.2

DIMDATA integration. Manage data, records, and automate workflows. Use when the user wants to interact with DIMDATA data.

0· 126·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description promise (DIMDATA integration) matches the instructions: all runtime actions use the Membrane CLI to discover connectors, create connections, run actions, or proxy API requests to DIMDATA. Nothing required by the skill is unrelated to that purpose.
Instruction Scope
SKILL.md stays within scope: it instructs installing and using the Membrane CLI, logging in via browser (or headless flow), listing/connecting to DIMDATA, running actions, and using a proxy. It does not ask the agent to read local secrets, arbitrary files, or exfiltrate data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec). It tells the user to install the Membrane CLI with a global npm install (or use npx). Installing a third-party npm CLI globally is a normal step for CLI-based integrations but carries the usual supply-chain risk of npm packages; the instruction itself is expected for this integration.
Credentials
The skill declares no required environment variables or credentials and explicitly instructs to rely on Membrane for credential management. That is proportionate for a connector-based integration and avoids asking for user API keys locally.
Persistence & Privilege
The skill does not request elevated persistence (always is false) and gives no guidance to modify other skills or global agent settings. Autonomous invocation remains allowed (platform default) but is not combined with other red flags.
Assessment
This skill looks coherent: it relies on the Membrane CLI to manage DIMDATA connectivity and explicitly avoids local secret handling. Before installing or running commands, verify the @membranehq/cli npm package and the getmembrane.com project (review the npm package page, vendor website, and GitHub repo) to ensure they're legitimate. Prefer using npx or a containerized environment instead of a global npm install if you want to avoid changing system state. Also confirm that you are comfortable giving your Membrane account permissions to access DIMDATA data, since Membrane will act as the proxy for API requests.

Like a lobster shell, security has layers — review code before you run it.

latestvk9722gpvzjm0y4fcm868p1jk3x84263z

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments