Nginx

v1.0.0

NGINX integration. Manage data, records, and automate workflows. Use when the user wants to interact with NGINX data.

0· 58·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
medium confidence
Purpose & Capability
Name and description match the instructions: the SKILL.md explains how to use the Membrane CLI to manage NGINX connections and actions. There are no unrelated environment variables, binaries, or install specs required beyond the membrane CLI.
Instruction Scope
Instructions stay within the stated purpose (install membrane CLI, login, create connections, list/run actions, or proxy requests). Important note: proxying via Membrane means API calls, configuration, and logs for your NGINX instance will be routed through Membrane's service — the skill explicitly relies on that behavior. The instructions do not ask for unrelated files or credentials.
Install Mechanism
No packaged install spec in the registry (instruction-only). SKILL.md tells users to install @membranehq/cli globally via npm (npm install -g). This is a standard approach but carries the usual implications of installing a global npm package (writes to system locations, requires appropriate privileges). The package comes from the public npm registry (not a raw URL), which is moderate risk but expected for a CLI.
Credentials
The skill requests no environment variables or local credentials; it relies on Membrane to manage authentication server-side. That is proportionate to the stated purpose. Consider the privacy/trust implications since credentials and proxied requests are managed by the third party rather than stored locally.
Persistence & Privilege
Skill is not forced-always, and uses normal agent invocation. It does not request system-wide configuration, nor does it instruct modifying other skills. No elevated persistence or privileges are requested by the skill itself.
Assessment
This skill is a coherent, instruction-only integration that tells you to use the Membrane CLI to connect to and manage NGINX. Before installing or using it: 1) Understand that requests and credentials will be proxied and managed by Membrane (a third party) — if your NGINX instance serves sensitive config or logs, confirm you trust Membrane and review their privacy/security documentation and terms. 2) Installing the CLI installs a global npm package (npm install -g) — be aware of system-level write/permission implications and prefer a vetted environment (or use npx to avoid global installs). 3) The skill does not request local secrets, but the authentication flow opens a browser and stores credentials in Membrane; verify the connection IDs and audit what data flows through the proxy. 4) If you require stricter control, consider using direct API calls to your NGINX endpoints instead of a third-party proxy, or validate the Membrane repo and package integrity before use. If you want a higher-assurance verdict, provide the package repository URL for @membranehq/cli or a link to Membrane's security documentation so those can be reviewed.

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

latestvk9764wvkgq8dq9sma1m7zrseyd84a2x4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments