Invision Community
v1.0.0Invision Community integration. Manage data, records, and automate workflows. Use when the user wants to interact with Invision Community data.
⭐ 0· 54·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 say 'Invision Community integration' and the SKILL.md exclusively instructs using the Membrane CLI to discover/connect to Invision and proxy API requests. Required capabilities (network access, a Membrane account) match the described purpose.
Instruction Scope
Runtime instructions focus on installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests. They do not ask the agent to read unrelated files, harvest system credentials, or post data to unknown endpoints; auth is handled via Membrane's browser flow as documented.
Install Mechanism
The doc recommends installing an npm global package (npm install -g @membranehq/cli) or using npx. This is a standard, traceable mechanism (npm registry / GitHub repo referenced), but installing global npm packages does write binaries to disk — consider using npx or reviewing the package source before global installation.
Credentials
No environment variables, local config paths, or unrelated credentials are requested. The skill relies on a Membrane account and browser-based login; that scope is proportionate to the stated functionality.
Persistence & Privilege
Skill is instruction-only, has no 'always' presence, and does not request persistent modification of agent/system-wide settings. Normal autonomous invocation is allowed but not excessive given the skill's role.
Assessment
This skill is coherent: it delegates auth and API calls to the Membrane CLI. Before installing, consider: (1) using npx instead of a global npm install to avoid writing binaries to disk, (2) reviewing the @membranehq/cli package (npm page/GitHub repo) to verify maintainership, and (3) understanding that authentication happens via a browser flow to Membrane — ensure you trust the Membrane service and account. If you prefer not to give any third-party service access to your community, don't create a Membrane connection and avoid installing the CLI.Like a lobster shell, security has layers — review code before you run it.
latestvk9760wj62qycq5wehx3bh29ffs84epvy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.