Aivie
v1.0.2Aivie integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aivie data.
⭐ 0· 106·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
high confidencePurpose & Capability
The skill is an integration for Aivie and explicitly instructs use of the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Aivie. No unrelated services, env vars, or system capabilities are requested.
Instruction Scope
SKILL.md contains concrete membrane CLI commands for login, searching connectors, listing actions, running actions, and proxying requests. It does not instruct reading arbitrary files, scraping unrelated environment variables, or exfiltrating data to unexpected endpoints. It does rely on browser-based auth or a headless URL/code flow as expected for OAuth-like flows.
Install Mechanism
The skill is instruction-only (no automatic install), but directs the user to install @membranehq/cli via npm or use npx. Installing a third-party CLI globally has standard risks (supply-chain, privilege of the CLI). This is proportionate for the described functionality but users should review the Membrane CLI package and prefer npx or pinned versions if concerned.
Credentials
No environment variables, system config paths, or credentials are requested by the skill itself. The instructions explicitly state Membrane manages credentials server-side and advise not to ask for API keys — this matches the integration model.
Persistence & Privilege
The skill is not force-included (always:false) and does not request persistent system privileges or modifications to other skills. Autonomous invocation is allowed by default but is not combined with other concerning privileges.
Assessment
This skill appears coherent and implements Aivie access via the Membrane CLI. Before use: (1) confirm you trust Membrane (getmembrane.com) and review the @membranehq/cli npm package (or use npx) to reduce supply-chain risk; (2) be aware that Membrane acts as a proxy and will have access to Aivie data once you create a connection—review connection scopes and permissions in the Membrane/Aivie auth flow; (3) avoid pasting service credentials into chat; use the documented connection flow so credentials are handled server-side.Like a lobster shell, security has layers — review code before you run it.
latestvk974d1b1x6w4gkrr6w6wdhjy9s842wee
License
MIT-0
Free to use, modify, and redistribute. No attribution required.