Infinity
v1.0.2Infinity integration. Manage Workspaces. Use when the user wants to interact with Infinity data.
⭐ 0· 102·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 (Infinity integration) matches the instructions: all runtime actions use the Membrane CLI and Membrane's proxy to interact with Infinity. No unrelated services, credentials, or binaries are requested.
Instruction Scope
SKILL.md narrowly instructs installing and using the Membrane CLI, logging in, creating/looking up connections, running pre-built actions, and optionally proxying raw Infinity API requests via Membrane. It does not instruct reading arbitrary host files or exfiltrating unrelated data.
Install Mechanism
The skill is instruction-only (no install spec), which is low-risk, but it instructs the user to run `npm install -g @membranehq/cli` to obtain the CLI. Installing a global npm package is a normal step but downloads code from the npm registry — verify the package and publisher before installing.
Credentials
The skill declares no required env vars or credentials; it delegates auth to Membrane and explicitly recommends not collecting user API keys locally. Requested access (a Membrane account) is proportional to the stated purpose.
Persistence & Privilege
The skill is not always-on and does not request persistent system privileges or modify other skills. Autonomous invocation is allowed (platform default) but not combined with other high-risk requests.
Assessment
This skill appears coherent and limited in scope, but before installing: (1) verify the @membranehq/cli package and publisher on the npm registry (installing a global npm package runs third-party code), (2) understand that Membrane will handle authentication and will be able to access your Infinity data via the connection you create, and (3) only proceed if you trust Membrane (check the homepage/repository and maintainers). If you need stricter control, avoid using the proxy/raw API path and prefer pre-built actions that limit what is sent to external endpoints.Like a lobster shell, security has layers — review code before you run it.
latestvk9747k0nwbhfmamvw7mnavmeqn843y0e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.