Edrone
v1.0.2Edrone integration. Manage data, records, and automate workflows. Use when the user wants to interact with Edrone data.
⭐ 0· 90·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 skill's name and description (Edrone integration) match the instructions: it uses Membrane to connect to Edrone and run actions. However, the registry metadata lists no required binaries even though the runtime instructions require installing and running the Membrane CLI (npm / membrane). This omission is a minor inconsistency.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying API requests to Edrone. It explicitly advises against asking users for API keys and uses browser-based auth flows. It does not instruct reading unrelated local files or exfiltrating environment variables.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the instructions ask the user to run `npm install -g @membranehq/cli`. That is a standard but persistent install mechanism and introduces the typical trust/verification requirement for third-party npm packages. The registry should have declared this binary dependency; users should verify the package and source before global installation.
Credentials
The skill declares no required env vars or credentials and the instructions state Membrane handles auth server-side (browser login flow). No unrelated secrets or config paths are requested. This is proportionate to the stated purpose.
Persistence & Privilege
The skill itself does not request always:true and is user-invocable. Installing the Membrane CLI is persistent on the host and the CLI will store authentication state for connections; this is expected for a CLI-based integration but is a persistence consideration the user should be aware of.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to access Edrone and does not ask for unrelated credentials. Before installing or using it, verify the @membranehq/cli package and its publisher (review the npm package page and the GitHub repo), prefer using npx for one-off runs instead of a global npm install if you want to avoid persistent system changes, and be aware that Membrane’s backend will mediate and store auth for the Edrone connection (so review Membrane's privacy and security practices). Also note the registry metadata omitted declaring the CLI dependency — confirm your environment can safely run the CLI and that you trust the Membrane service before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk974dcd7cf3egrkkt92x2sh8vd842kkj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.