Amity
v1.0.0Amity integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amity data.
⭐ 0· 94·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 (Amity integration) align with the instructions: all commands use the Membrane CLI to discover and run Amity-related actions. Nothing requested is unrelated to interacting with Amity via Membrane.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, running connectors/actions, and proxying requests to Amity. However, using Membrane means your Amity requests and related data will be routed through Membrane's servers — a privacy/trust consideration mentioned in the docs.
Install Mechanism
No install spec is embedded in the skill (instruction-only), but the SKILL.md instructs a global npm install (@membranehq/cli). Global npm installs run code from the npm registry and require elevated write permissions on some systems; verify the package and its provenance before installing.
Credentials
The skill does not request environment variables, credentials, or config paths. It explicitly defers auth to Membrane rather than asking for API keys — the requested access matches the stated purpose.
Persistence & Privilege
The skill does not request always:true or any elevated persistence. It's user-invocable and uses the host's Membrane CLI at runtime; there is no indication it modifies other skills or global agent configs.
Assessment
This skill delegates Amity access through the third-party Membrane service and asks you to install the @membranehq/cli package globally. Before installing/use: (1) Verify you trust Membrane (review privacy, terms, and where requests will be routed), (2) confirm the npm package name and version on the official registry or repo, (3) prefer installing the CLI in a controlled environment (avoid global installs on sensitive machines if possible), (4) do not hand over API keys locally — the skill intends for Membrane to manage auth — and (5) consider using a limited-scope/test Amity account to reduce risk and monitor activity/logs the first time you use it.Like a lobster shell, security has layers — review code before you run it.
latestvk976y0176xj0830cc84h6kef9d84hcq6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.