U301
v1.0.0U301 integration. Manage data, records, and automate workflows. Use when the user wants to interact with U301 data.
⭐ 0· 54·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description claim a U301 integration implemented via the Membrane CLI; the SKILL.md consistently instructs use of @membranehq/cli to connect, list actions, run actions, and proxy requests — this matches the stated purpose. Minor inconsistency: SKILL.md lists "Official docs: https://support.usa.canon.com/", which looks unrelated to Membrane/getmembrane and may be a mistaken or placeholder link.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI (login, create connection, list/run actions, proxy requests). They do not instruct reading local files, collecting unrelated environment variables, or exfiltrating data to unexpected endpoints. They do rely on network access and browser-based auth flows.
Install Mechanism
There is no formal install spec in the skill bundle (it is instruction-only). The SKILL.md recommends installing a global npm package (@membranehq/cli). Installing packages from npm is a normal but non-trivial action because it runs third-party code on your machine — this is expected for a CLI-based integration but carries the usual npm package risk.
Credentials
The skill requests no environment variables or local credentials and explicitly states Membrane handles authentication server-side. That is proportionate to the described approach (delegating auth to Membrane).
Persistence & Privilege
The skill does not request always:true, does not ship code, and is user-invocable only. It does not request elevated or persistent system privileges beyond suggesting a CLI install that the user performs.
Assessment
This skill appears to be a straightforward Membrane-based adapter for "U301" and is instruction-only. Before installing or using it: 1) Confirm you trust the @membranehq CLI package and the Membrane provider (review the npm package page and the repository URL). 2) Prefer using npx or a per-project install rather than a global `npm install -g` if you want to limit system-wide changes. 3) Be aware the login flow opens a browser and grants Membrane access to the connected service — ensure you’re comfortable delegating auth to that provider. 4) The SKILL.md includes an unrelated Canon support link; validate the correct target API/docs for your U301 system. If anything about the package, homepage, or repository looks untrusted, do not install the CLI or create connections.Like a lobster shell, security has layers — review code before you run it.
latestvk97bry0ky3vgyaanmemqkv56td84crzm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.