Munity
v1.0.0Munity integration. Manage data, records, and automate workflows. Use when the user wants to interact with Munity data.
⭐ 0· 52·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 name/description (Munity integration) align with the runtime instructions: all operations are Munity-related and performed via the Membrane CLI. Minor inconsistency: the registry metadata lists no required binaries, yet the SKILL.md expects the membrane CLI (npm package) to be installed.
Instruction Scope
SKILL.md confines the agent to installing/using the Membrane CLI, creating connections, listing/running actions, and proxying requests to the Munity API. All actions are within the stated purpose. The proxy feature can issue arbitrary requests to Munity via the connection (expected for an integration).
Install Mechanism
No install spec is declared in the registry, but the SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a moderate-risk operation (code from the public npm registry). This is not inherently malicious but is an operational mismatch that you should notice.
Credentials
The skill requests no environment variables or credentials in metadata. The SKILL.md explains that Membrane manages auth server-side and advises not to ask users for API keys, which is proportionate. Note: creating a Membrane connection grants Membrane access to the user's Munity account on their behalf—this is expected but worth reviewing.
Persistence & Privilege
always is false and there are no required config paths or other persistent privileges requested. The skill can be invoked autonomously (platform default), which is normal; this combined with other flags does not raise extra concern here.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to connect to Munity and run actions. Before installing or running it, verify you trust the Membrane project and the npm package (@membranehq/cli): review the package source/release, prefer installing in a controlled environment (docker/sandbox) rather than global -g if possible, confirm what permissions the Membrane OAuth/connection will grant to your Munity data, and avoid pasting unrelated secrets into the tool. The registry metadata omission of a required binary is a small red flag — ensure the runtime dependency (membrane CLI) is available and safe in your environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97dz6y11ffxhm5k86ktg0ehd184fj9w
License
MIT-0
Free to use, modify, and redistribute. No attribution required.