ClawHub

Browse Ai

v1.0.2

Browse AI integration. Manage data, records, and automate workflows. Use when the user wants to interact with Browse AI data.

⭐ 0· 95·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description describe a Browse AI integration and the SKILL.md exclusively instructs using the Membrane CLI to connect to Browse AI and run actions — the requested capabilities match the stated purpose.
✓
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, performing login flows, listing/searching connectors, running actions, and proxying requests to Browse AI. The doc does not instruct reading unrelated files, requesting unrelated env vars, or exfiltrating data to unexpected endpoints.
ℹ
Install Mechanism
The skill recommends installing @membranehq/cli globally via npm (npm install -g). This is a standard approach but carries the usual risks of installing third-party CLIs (supply-chain risk, global install privileges). No direct download URLs or archives are used; risk is moderate but proportionate.
✓
Credentials
The skill requests no environment variables or credentials and advocates using Membrane's browser-based auth flow (no local API keys). Credential requirements are minimal and appropriate for an integration that delegates auth to Membrane.
✓
Persistence & Privilege
Skill is instruction-only, has no install-time persistence, and does not request 'always: true' or other elevated privileges. It can be invoked by the model (default), which is normal for skills.
Assessment
This skill is coherent and appears to do what it says: it drives Browse AI via the Membrane CLI. Before installing, verify the npm package @membranehq/cli is the official package (check the publisher and repository), and be aware that installing a global npm CLI can require elevated permissions and runs code on your machine. The auth flow opens a browser and delegates credential storage to Membrane — confirm you trust the Membrane service and its homepage/repository. If you want stricter assurances, review the Membrane CLI source on GitHub and any npm package metadata before installing.

Like a lobster shell, security has layers — review code before you run it.

latestvk9777735p0mmja8gggm0jpqp4s842wv0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments