Prerenderio
v1.0.2Prerender.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Prerender.io data.
⭐ 0· 78·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
Name/description (Prerender.io integration) match the instructions: the skill directs the agent to use the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to prerender.io. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md confines runtime behavior to running the Membrane CLI, creating connections, listing/running actions, and proxying requests to the Prerender.io API. It does not instruct reading arbitrary local files, harvesting environment variables, or sending data to unexpected endpoints beyond the Membrane proxy and Prerender.io.
Install Mechanism
There is no automated install spec in the bundle (instruction-only), but the SKILL.md tells users to run `npm install -g @membranehq/cli` (or use npx). Installing a global npm package is a moderate supply-chain risk because it downloads and runs third-party code; this is expected for a CLI-based integration but worth user scrutiny.
Credentials
The skill declares no required env vars or credentials and instructs users to authenticate via Membrane (browser OAuth flow). This is consistent: Membrane is intended to manage credentials server-side so the skill itself does not request unrelated secrets.
Persistence & Privilege
The skill is instruction-only, does not request persistent presence (always: false), and does not modify other skills or system-wide settings. Autonomous invocation is allowed but that is the platform default and not by itself concerning here.
Assessment
This skill appears to do what it says: use the Membrane CLI to talk to Prerender.io. Before installing or running it, verify the @membranehq npm package publisher and read the package's README/repository to ensure it is legitimate; prefer running one-off npx commands instead of a global install if you want less system impact. Understand that creating a Membrane connection grants Membrane (and any connectors it manages) the ability to act on your behalf for Prerender.io — review the connection scope and revoke it if you no longer need it. If you're unsure, run CLI commands in an isolated or test environment first and avoid entering unrelated secrets or pasting credentials into places not explicitly required by Prerender.io or Membrane.Like a lobster shell, security has layers — review code before you run it.
latestvk97541mwaaba81d4b58bym8cnh8424tm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.