1Forge
v1.0.21Forge integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1Forge 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
high confidencePurpose & Capability
The name/description (1Forge data access) match the instructions: all actions are about installing and using the Membrane CLI to connect to 1Forge, list actions, run actions, and proxy requests. Nothing requests unrelated cloud credentials or system access.
Instruction Scope
Instructions are narrowly scoped to installing the Membrane CLI, logging in, creating a connection, discovering and running actions, and proxying API calls. One important behavioral note: proxying and action executions send requests and authentication information through Membrane's service (server-side), so data and tokens will transit/ be stored by Membrane — this is expected for this integration but is a privacy/operational consideration.
Install Mechanism
There is no built-in install spec; the SKILL.md instructs users to install the Membrane CLI via npm (npm install -g @membranehq/cli). That is a conventional delivery mechanism for a CLI but does perform a global install on the host. No arbitrary downloads, extract steps, or unknown URLs are required by the skill itself.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The instructions explicitly advise against collecting API keys locally and instead rely on Membrane-managed connections — the requested access is proportional to the stated purpose.
Persistence & Privilege
The skill is instruction-only, has no always:true flag, and does not modify other skills or system-wide agent settings. It requires a one-off CLI install and uses the Membrane login flow; it does not request elevated or persistent platform privileges.
Assessment
This skill is coherent and relies on the Membrane CLI to act as a proxy between you and 1Forge. Before installing: (1) verify you trust Membrane (getmembrane.com) because API requests and credentials will be handled by their service; (2) confirm you are comfortable running a global npm install (@membranehq/cli) on your machine; (3) avoid sending unrelated sensitive data through the proxy; (4) when authenticating, use the official Membrane login flow and inspect the connection IDs and permissions you grant. If you need to avoid routing data through a third party, do not use this skill and call 1Forge directly with your own API key instead.Like a lobster shell, security has layers — review code before you run it.
latestvk976mhej9140wexb2raf876tnx842gfj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.