Datatrails
v1.0.0DataTrails integration. Manage data, records, and automate workflows. Use when the user wants to interact with DataTrails data.
⭐ 0· 67·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description state a DataTrails integration and the SKILL.md consistently instructs using the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to DataTrails. Required capabilities (a networked Membrane account and the CLI) align with the stated purpose.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI, authenticating, discovering actions, running them, and proxying requests. They do not ask to read unrelated files or environment variables. Note: the proxy feature lets the agent send arbitrary API requests through Membrane to endpoints available via the connection — this is expected for a proxy but gives broad API access within the connected service.
Install Mechanism
This is an instruction-only skill (no install spec), but the docs tell the user to run `npm install -g @membranehq/cli`. That is coherent (a CLI is needed) but installing a global npm package writes code to disk and runs it on the user's machine — verify package provenance before installing.
Credentials
The skill requests no environment variables or local config paths. It delegates credential handling to Membrane (browser-based login/connection creation), which is consistent with its advice to avoid asking users for API keys.
Persistence & Privilege
The skill is not always-on and uses normal autonomous-invocation defaults. It does not request persistent system privileges or attempt to modify other skills/configs in the manifest.
Assessment
This skill appears coherent: it requires the Membrane CLI and a Membrane/DataTrails account, which matches the stated purpose. Before installing or following the instructions: verify the @membranehq/cli package on npm and the Membrane project repository (and prefer installing in a controlled environment or container if you are unsure), confirm getmembrane.com and the GitHub repository are legitimate, and be aware that the CLI login creates an authenticated connection that lets Membrane proxy API calls on your behalf (so only grant access if you trust the Membrane service and the connector's permissions). Avoid running global installs as root where possible and review the CLI's code or release notes if you need higher assurance.Like a lobster shell, security has layers — review code before you run it.
latestvk9766gehpdtcqmgqkjxybvjsdh845e9x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.