Go Upc
v1.0.2Go-UPC integration. Manage Organizations. Use when the user wants to interact with Go-UPC data.
⭐ 0· 109·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
high confidencePurpose & Capability
The skill's stated purpose (Go-UPC integration) matches the instructions (use the Membrane CLI to connect to Go-UPC). One minor inconsistency: the registry metadata lists no required binaries, but the SKILL.md expects npm (to install the CLI) and the 'membrane' CLI to be available. This is a documentation gap rather than a functional mismatch.
Instruction Scope
SKILL.md confines the agent to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Go-UPC. It does not instruct reading unrelated files, exporting environment variables, or sending data to unexpected endpoints. It does instruct interactive/browser-based authentication and a headless URL/code flow.
Install Mechanism
There is no formal install spec in the registry; installation is described in the instructions as 'npm install -g @membranehq/cli' (public npm). Installing from the npm registry is common but carries the moderate supply-chain risk inherent to public packages; the skill should have declared its dependency on npm/node and the external CLI in metadata.
Credentials
The skill declares no required environment variables or secrets and the instructions explicitly advise not to request API keys (Membrane handles auth server-side). There are no unexpected credential requests or config paths.
Persistence & Privilege
The skill does not request 'always: true' or other elevated persistence. It is user-invocable and can be run autonomously by the agent (platform default), which is appropriate for this kind of integration.
Assessment
This skill is instruction-only and directs you to install and use the Membrane CLI to connect to Go-UPC. Before installing: verify the @membranehq/cli package and the Membrane project pages (the SKILL.md points to getmembrane.com and a GitHub repo), and be aware 'npm install -g' modifies your system-wide packages (requires appropriate privileges). If you want lower install friction or to avoid a global npm install, consider using npx or a local install. Expect the CLI to open a browser for authentication (or provide a headless code flow). The skill does not ask for API keys and relies on Membrane to manage credentials server-side. If you require stricter supply-chain assurance, ask the publisher for a formal install spec, checksums, or to host releases on a verifiable release channel before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk977tj9y0m9y7vgynn427a0g6n8432fq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.