Bigid
v1.0.0BigID integration. Manage data, records, and automate workflows. Use when the user wants to interact with BigID data.
⭐ 0· 55·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 skill declares itself as a BigID integration but explicitly uses the Membrane CLI to talk to BigID. Requiring a Membrane account and network access is coherent with that design: the skill delegates authentication and API access to Membrane rather than requesting BigID credentials directly.
Instruction Scope
SKILL.md instructs using the Membrane CLI and a Membrane account; this keeps the skill's runtime actions within the stated scope (install/operate a CLI and call BigID via Membrane). The provided excerpt does not show instructions to read unrelated system files or additional env vars, but the full SKILL.md should be reviewed for any steps that access unrelated files or network endpoints besides Membrane/BigID.
Install Mechanism
There is no install spec in the skill bundle (instruction-only). The runtime instructions tell the user to install the Membrane CLI from getmembrane.com. That is a reasonable approach but it means installation and execution of third-party code occurs outside the skill bundle and relies on the trustworthiness of Membrane's distribution.
Credentials
The skill declares no required env vars or credentials. Instead it relies on a Membrane account/CLI to manage BigID credentials. This is proportionate, but it centralizes secrets in the Membrane service/CLI — users should verify how and where Membrane stores credentials and whether that matches their security/privacy requirements.
Persistence & Privilege
The skill does not request always:true, does not ship code that writes to disk as part of an install spec, and is user-invocable. Nothing in the bundle requests elevated or permanent platform-wide privileges.
Assessment
This skill is coherent: it implements BigID access through the Membrane CLI rather than embedding BigID credentials. Before installing or following its instructions, verify getmembrane.com is the official Membrane distribution, review the Membrane CLI's installation and permissions, and confirm where Membrane will store/handle your BigID credentials (and whether that storage meets your organization's security policy). If you prefer not to trust an intermediary, look for a skill that connects directly to BigID (and then expect direct BigID credentials to be requested). Also review the full SKILL.md for any commands that access system files or send data to endpoints other than Membrane/BigID.Like a lobster shell, security has layers — review code before you run it.
latestvk972x6fhwsry3e2z31hrx88eb18454a3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.