Frameio
v1.0.2Frame.io integration. Manage Projects, Teams. Use when the user wants to interact with Frame.io data.
⭐ 0· 126·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 skill's name/description (Frame.io integration) match the instructions: it uses Membrane to connect, discover actions, run actions, and proxy API requests to Frame.io. Nothing in the SKILL.md requests unrelated cloud credentials or system access beyond network and a Membrane account.
Instruction Scope
Instructions are focused on installing and using the Membrane CLI (login, connect, action list/run, proxy). They do not instruct reading arbitrary files or environment variables. Note: the SKILL.md tells the user to run 'npm install -g @membranehq/cli' and browser-based login; the skill metadata did not declare npm or a Node.js runtime as a required binary.
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing an npm package globally. Installing a global npm package requires network access and may require elevated permissions on some systems; the package is from the @membranehq scope (public registry) which is expected for this integration but should be verified by the user.
Credentials
The skill declares no environment variables or credentials and explicitly advises letting Membrane handle API keys. This is proportionate for a proxy/connector-based integration. Be aware that Membrane (the service) will hold and manage the Frame.io credentials when you create a connection.
Persistence & Privilege
The skill is not always-enabled, does not request elevated persistence, and does not instruct modification of other skills or global agent configuration. Normal autonomous invocation is allowed by platform defaults but is not an extra privilege here.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to connect to Frame.io and run actions. Before installing/using it you should: 1) confirm you trust Membrane (getmembrane.com / @membranehq) because Membrane will proxy API calls and hold your Frame.io credentials; 2) verify the npm package name (@membranehq/cli) and its source (official repo) before running a global npm install — global installs may require admin rights; 3) be aware the SKILL.md expects npm/Node.js and a browser-based login flow even though the skill metadata did not list npm as a required binary; 4) if you need stronger privacy, consider creating limited-scope Frame.io credentials and review Membrane's privacy/security docs. Overall the skill is coherent and there are no other red flags.Like a lobster shell, security has layers — review code before you run it.
latestvk975fh9z7wj5nkt2tqf339rmjh843nd8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
