Datawrapper
v1.0.0Datawrapper integration. Manage data, records, and automate workflows. Use when the user wants to interact with Datawrapper data.
⭐ 0· 53·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 Datawrapper and the SKILL.md exclusively describes using the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests — all coherent with a Datawrapper integration.
Instruction Scope
Instructions stay on-topic: they instruct installing and using the Membrane CLI, logging in, creating a Datawrapper connection, listing actions, running actions, and proxying requests. There are no directives to read unrelated files, export local secrets, or contact unexpected endpoints. The doc explicitly advises not to ask users for API keys.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal approach for a CLI but has moderate operational risk (writes to disk, may require elevated privileges, and relies on the npm package supply chain). The target package appears to be the official Membrane CLI; verifying the package source and maintainers is recommended before global install.
Credentials
The skill declares no required environment variables or credentials. However, it does rely on Membrane to store and proxy Datawrapper credentials server-side — meaning Datawrapper access tokens will be managed by the Membrane service rather than local env vars. Users should be aware that Datawrapper data and auth will flow through Membrane's infrastructure.
Persistence & Privilege
The skill does not request always:true or any system-wide config changes. It is user-invocable and allows normal autonomous invocation behavior (platform default). Nothing in the SKILL.md attempts to modify other skills or system-wide settings.
Assessment
This skill is coherent and appears to do what it says: use Membrane's CLI to manage a Datawrapper connection and run actions. Before installing or using it: 1) Verify you trust Membrane (https://getmembrane.com) because Datawrapper credentials and request payloads will be proxied and stored by their service. 2) Inspect the @membranehq/cli package on npm/GitHub (maintainers, recent releases, integrity) before running a global `npm install -g`. 3) If you have strict data residency or compliance needs, confirm that routing Datawrapper traffic through Membrane is acceptable. 4) Prefer running the CLI in a controlled environment (not a shared CI runner) and avoid pasting secrets into chat. If any of these conditions are unacceptable, do not install or connect through Membrane.Like a lobster shell, security has layers — review code before you run it.
latestvk979brxhz4r29hd1bcfegxewbh848sq4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.