Hiveage
v1.0.2Hiveage integration. Manage Users, Organizations. Use when the user wants to interact with Hiveage data.
⭐ 0· 111·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 name/description (Hiveage integration) aligns with the runtime instructions: all actions use the Membrane CLI to list/connect/run Hiveage-related actions. No unrelated services, credentials, or binaries are requested.
Instruction Scope
SKILL.md limits behavior to installing/using the Membrane CLI, logging in, creating/listing connections, running actions, and proxying requests to the Hiveage API. It does not instruct reading arbitrary files, scanning unrelated env vars, or sending data to external endpoints outside Membrane/Hiveage.
Install Mechanism
The registry has no formal install spec, but the instructions advise `npm install -g @membranehq/cli`. That is a public npm package install (traceable but requiring privilege to install globally). This is expected for a CLI-driven integration but carries the usual risk of trusting a third-party npm package and granting it a global install location.
Credentials
The skill declares no required environment variables or credentials; it relies on Membrane's interactive/browser-based auth flow. Requested access is proportionate to the stated purpose (accessing Hiveage via Membrane).
Persistence & Privilege
always is false and the skill is user-invocable. There is no instruction to modify other skills or global agent configs. No elevated or persistent privileges are requested by the SKILL.md itself.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to talk to Hiveage. Before installing or following the doc, verify you trust the Membrane project/package (review the npm package page and GitHub repo), be aware that `npm install -g` installs code system-wide (consider a local install or container if you prefer), and understand that Membrane will mediate and store authentication for Hiveage — treat those connections like any third-party OAuth/API token (revoke when no longer needed). If you need higher assurance, inspect the @membranehq/cli source/release on GitHub and confirm the connector IDs and endpoints correspond to Hiveage.Like a lobster shell, security has layers — review code before you run it.
latestvk974jqsckmnewj5bvwwesht44s842aeq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.