Urlbae
v1.0.2UrlBae integration. Manage data, records, and automate workflows. Use when the user wants to interact with UrlBae data.
⭐ 0· 119·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
Name/description claim UrlBae integration and all runtime instructions are about discovering and running Membrane-provided UrlBae actions or proxying to the UrlBae API via Membrane. Required capabilities (network access and a Membrane account/CLI) align with the stated purpose.
Instruction Scope
SKILL.md exclusively instructs installing and using the Membrane CLI, performing 'membrane login', creating connections, listing actions, running actions, and proxying requests. It does not direct the agent to read unrelated files, harvest system secrets, or exfiltrate data to unexpected endpoints. It does require interactive login via a browser (or headless flow).
Install Mechanism
No install spec in the skill bundle, but the instructions recommend installing the official @membranehq/cli from npm (npm install -g). Using npm is a common approach but installing global npm packages executes code on the machine — users should verify the package name/publisher and/or review the CLI source before global installation.
Credentials
The skill declares no environment variables or credentials. It relies on Membrane to manage auth; this is proportionate. Note: using Membrane means the service (and its connectors) will see proxied API requests and can manage credentials server-side, so trust in the Membrane service is required.
Persistence & Privilege
always:false and default autonomous invocation are appropriate. The skill does not request persistent system-wide configuration or access to other skills' credentials.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with UrlBae and does not request unrelated secrets. Before installing: (1) verify the npm package @membranehq/cli exists and is published by the expected maintainer (review the package page or GitHub repo), (2) understand that Membrane will proxy API requests and therefore can see the data and manage credentials on your behalf, so only route data you trust through it, (3) if you are cautious about global installs, consider installing the CLI in a contained environment (container or VM) or using npx, and (4) do not provide local API keys to this skill — follow the described connection/login flow so credentials are handled by Membrane.Like a lobster shell, security has layers — review code before you run it.
latestvk97bgx2brpck5gqhk35n70vm8584288a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.