Netlify
v1.0.2Netlify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Netlify data.
⭐ 0· 134·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
Name/description (Netlify integration) matches the instructions: all actions are performed via the Membrane CLI and Membrane connections to Netlify. The skill does not request unrelated environment variables or system-level resources.
Instruction Scope
SKILL.md limits activity to installing/using the Membrane CLI, logging in (browser-based OAuth flow), creating/listing connections, running predefined Membrane actions, and optionally proxying requests to the Netlify API. It does not instruct reading arbitrary filesystem files, harvesting env vars, or sending data to unexpected endpoints.
Install Mechanism
No install spec in the registry; SKILL.md recommends installing @membranehq/cli via `npm install -g`. Global npm install is expected for a CLI but will write binaries to disk and requires network access — this is proportionate but users should be aware of the usual risks of installing global npm packages from the public registry.
Credentials
The skill declares no required env vars or credentials and relies on Membrane's login/connection flow to manage Netlify credentials. That is consistent and proportionate. Note: granting Membrane a connection to Netlify effectively gives Membrane (or the Membrane-managed token) access to the Netlify account per the permissions requested during OAuth.
Persistence & Privilege
always:false and no special persistence or modification of other skills is requested. The skill does not request elevated or permanent presence beyond normal agent-invocable behavior.
Assessment
This skill is instruction-only and appears coherent, but before installing: 1) confirm you trust Membrane (@membranehq) and the homepage/repository (npm package source) because the Membrane service will hold tokens and act on your Netlify account; 2) be aware you will need to install a global npm CLI and perform a browser OAuth login that grants Membrane access to Netlify — review the permissions requested during that flow; 3) treat Membrane as the party that will have API-level access to your Netlify data (avoid giving direct Netlify API keys to the skill); and 4) if you require higher assurance, inspect the @membranehq/cli package source on its official repo or install in a sandboxed environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk975kxg8ncqv0qzxycxrqnhxgd8421bx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.