Dataddo
v1.0.2Dataddo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Dataddo data.
⭐ 0· 68·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 claims to integrate with Dataddo and the SKILL.md consistently instructs use of the Membrane CLI and Membrane proxy to manage Dataddo connections and run actions — these requirements match the stated purpose.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, performing login via browser, creating connections, listing actions, and proxying requests to Dataddo. They do not instruct reading unrelated system files, environment variables, or exfiltrating data outside the Membrane/Dataddo flow.
Install Mechanism
The skill is instruction-only (no install spec), but it recommends a global npm install (@membranehq/cli). This is expected for a CLI-based integration but has the usual risk of installing third-party npm packages globally — verify the package/source before installing.
Credentials
No environment variables or unrelated credentials are requested. The SKILL.md explicitly directs users to let Membrane manage credentials rather than supplying API keys locally, which is proportionate for this integration.
Persistence & Privilege
The skill does not request 'always' presence or elevated agent privileges. It only instructs the user to install and run a CLI; no skill-level persistent privileges are declared.
Assessment
This skill is coherent: it asks you to install and use the Membrane CLI to talk to Dataddo rather than handling raw API keys locally. Before installing or using it, verify you trust the Membrane project and the @membranehq/cli npm package (check the GitHub repo and package publisher), and understand that Membrane will broker and therefore have access to your Dataddo credentials/data. Installing global npm packages can affect your environment—prefer using a scoped or containerized environment if you want to limit system impact. If you need stronger assurance, confirm the repository and package integrity (official GitHub org, checksums, or package signatures) before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk977k8zdjrhtvkpffys0csj6798438nr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.