ClawHub

Droxy

v1.0.2

Droxy integration. Manage Organizations. Use when the user wants to interact with Droxy data.

⭐ 0· 124·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (Droxy integration) match the runtime instructions which use the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests to Droxy. Required resources (network access, a Membrane account) are reasonable for this purpose.
✓
Instruction Scope
SKILL.md confines itself to installing and using the Membrane CLI, performing browser-based login, listing/connecting actions, running actions, and proxying requests. It does not instruct reading unrelated local files, exfiltrating system data, or asking for unrelated secrets; it explicitly advises against asking users for API keys.
ℹ
Install Mechanism
The install guidance is to run `npm install -g @membranehq/cli`. This is an expected way to obtain a CLI but carries the usual npm-installed-package risk (third-party code installed globally). It's proportionate for a CLI-driven integration, but users should verify the package and publisher before installing on sensitive systems.
✓
Credentials
The skill declares no required environment variables, no primary credential, and no config-path access. Auth is handled via Membrane's browser login flow as described, which is consistent and avoids asking for local secrets.
✓
Persistence & Privilege
The skill does not request always-on inclusion and does not instruct modifying other skills or system-wide agent settings. It is user-invocable and may be invoked autonomously (platform default), which is expected for integrations.
Assessment
This skill is coherent: it uses the Membrane CLI to interact with Droxy and does not ask for unrelated credentials or filesystem access. Before installing the CLI, verify the npm package and publisher (@membranehq) are legitimate and acceptable for your environment (global npm installs run code on your machine). If you cannot or do not want to install global packages, run the CLI in a contained environment (container or VM) or ask for an alternative integration method.

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

latestvk971df3v0n4g72fdxvy32zw2ts842zzx

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments