Serverless
v1.0.2Serverless integration. Manage data, records, and automate workflows. Use when the user wants to interact with Serverless data.
⭐ 0· 242·1 current·1 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
The name/intro references the Serverless framework (serverless.com) but the runtime instructions consistently route actions through the Membrane CLI/proxy. This is coherent (Membrane is used as the connector), but the initial framing could confuse readers who expect a direct Serverless Framework integration.
Instruction Scope
All runtime instructions are limited to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Serverless APIs via Membrane. The skill does not instruct reading unrelated local files or exporting secrets.
Install Mechanism
There is no platform install spec (skill is instruction-only). The SKILL.md instructs users to run `npm install -g @membranehq/cli`, which is a normal but privileged global npm install; this is expected for a CLI-based integration but is a user-side action rather than an automated install.
Credentials
The skill declares no required environment variables or credentials and explicitly advises using Membrane connections rather than asking for API keys. Requested access (a Membrane account and network) is proportionate to the described functionality.
Persistence & Privilege
The skill does not set always:true and remains user-invocable; it does not request persistent system-wide changes or access to other skills' configs.
Assessment
This skill uses the Membrane CLI to mediate access to Serverless APIs. If you install it: (1) you or the agent will need to install a global npm package (npm install -g @membranehq/cli) and sign into a Membrane account; (2) Membrane will hold/refresh any upstream credentials, so you should only use this if you trust Membrane as a proxy for your Serverless environment; (3) be cautious when running or authorizing arbitrary proxy requests (membrane request ...) because those requests can access resources reachable by the connected account; and (4) do not provide local API keys or secrets to the agent—use the connection flow described by the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97fhqhxc6dz1xqpgf288dc26h8426nq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.