Belugacdn
v1.0.0BelugaCDN integration. Manage data, records, and automate workflows. Use when the user wants to interact with BelugaCDN data.
⭐ 0· 56·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
medium confidencePurpose & Capability
The name/description (BelugaCDN integration) aligns with the instructions: the skill uses the Membrane CLI to discover/connect to BelugaCDN connectors and run actions or proxied API requests. The operations requested (connector search, connection, action run, proxied requests) are appropriate for a CDN integration.
Instruction Scope
SKILL.md only instructs the agent to install and run the Membrane CLI and use it to manage connections and proxy requests to BelugaCDN. It does not ask the agent to read unrelated files, other credentials, or to exfiltrate arbitrary local data. Headless auth instructions are limited to copying/using a login code.
Install Mechanism
The skill instructs the user to run `npm install -g @membranehq/cli` (a public npm package). That is an expected install for this integration but is a third-party install step that writes to disk and adds a global binary; users should verify the package source (npm page / GitHub) before installing. There is no automated install spec in the registry metadata — installation is user-driven.
Credentials
The skill declares no required environment variables or credentials and explicitly recommends letting Membrane handle credentials rather than asking for API keys. This is proportionate: Membrane handles authentication server-side so local secrets aren't needed.
Persistence & Privilege
The skill is instruction-only and does not request persistent installation privileges or always-on presence. It does not modify other skills or system-wide agent configuration according to the provided files.
Assessment
This skill appears coherent for a Membrane-based BelugaCDN integration, but before installing: verify the @membranehq/cli npm package and its GitHub source, and prefer installing in a controlled environment (or using npx) if you don't want a global binary. Confirm you trust Membrane as the auth proxy (it will mediate API calls and hold credentials server-side). Note the registry metadata omitted the CLI requirement and a Membrane-account requirement — make sure you have network access and a Membrane account and be cautious installing global npm packages from unknown sources.Like a lobster shell, security has layers — review code before you run it.
latestvk973pp08gh53y4h9xnfz93trm58449fs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.