Hivebrite

v1.0.0

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

0· 32·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Hivebrite integration) align with the instructions: it uses the Membrane CLI to connect to Hivebrite, list actions, run actions, and proxy requests. Requiring a Membrane account and network access fits the declared purpose.
Instruction Scope
SKILL.md only instructs the agent/operator to install and use the Membrane CLI, log in via browser, list/connect/run actions, and proxy API requests through Membrane. It does not instruct reading unrelated files, requesting unrelated credentials, or transmitting data to unexpected endpoints beyond Membrane/Hivebrite.
Install Mechanism
There is no platform install spec (skill is instruction-only). The instructions recommend global installation via npm (npm install -g @membranehq/cli). Installing a global npm package is common but you should verify the package name/maintainer and trust @membranehq before installing system-wide.
Credentials
The skill declares no required env vars or keys and specifically tells users not to provide API keys. It relies on Membrane-managed authentication (browser OAuth). This is proportionate; however, using Membrane means a third-party service will mediate and see API requests/responses.
Persistence & Privilege
always is false and the skill is user-invocable (normal). The agent can invoke the skill autonomously (platform default). Be aware that autonomous runs plus network/CLI access allow calling Hivebrite via Membrane without local secrets, which is expected but increases operational impact if misused.
Assessment
This skill appears consistent and uses the Membrane CLI to handle authentication and proxying. Before installing/use: (1) verify the @membranehq package and its GitHub repo (ensure you're installing the official package), (2) understand that Membrane (getmembrane.com) will broker API requests and will see the data—review their privacy/security posture and what access the connection grants to your Hivebrite tenant, (3) prefer installing the CLI in a controlled environment (not as root/global if you cannot trust the package), and (4) review any Membrane connection permissions and limit access to only the data/actions needed. If you need higher assurance, ask for the exact Membrane connector ID and inspect the actions returned by membrane action list before letting the agent run actions autonomously.

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

latestvk979kjnczwnxnezrjb5vzap69x84677w

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments