Web3Forms Contact Forms For Static Websites
v1.0.2Web3Forms — Contact Forms for Static Websites integration. Manage data, records, and automate workflows. Use when the user wants to interact with Web3Forms —...
⭐ 0· 48·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
The name/description and runtime instructions align: the skill instructs the agent to use the Membrane CLI to discover/connect to a Web3Forms connector and run actions. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
Instructions are narrowly scoped to installing/using the Membrane CLI (login, connect, action list/run, request proxy). They do not instruct reading local files or unrelated env vars. Note: the guidance recommends using Membrane's proxy, which means form submission payloads will be routed through Membrane's service — this is expected for this integration but is a privacy/operational consideration the user should be aware of.
Install Mechanism
No install spec in the registry; the SKILL.md recommends installing the CLI via npm (-g) or using npx. Installing via npm is common/traceable (moderate risk); prefer using npx to avoid global installs if you want less system-wide change.
Credentials
The skill declares no required env vars or secrets and relies on Membrane to handle credentials and browser-based login. That is proportionate to its purpose. It does require network access and a Membrane account (declared in the SKILL.md).
Persistence & Privilege
always:false and no install writes or config path access are requested. The skill does not request elevated/persistent system privileges beyond using a CLI the user installs.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to connect to Web3Forms and run actions. Before installing, confirm you trust Membrane (its privacy/security practices) because form data and auth will flow through their service. Prefer invoking via npx to avoid global npm installs if you want to minimize system changes. Be prepared to authenticate through a browser (or the headless flow) and review the connector's requested permissions when creating the connection.Like a lobster shell, security has layers — review code before you run it.
latestvk972rvnfpavv7xchgqxkdx0vyd84277k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.