Gigalixir
v1.0.0Gigalixir integration. Manage data, records, and automate workflows. Use when the user wants to interact with Gigalixir data.
⭐ 0· 46·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
Name/description (Gigalixir integration) match the instructions: all runtime actions call the Membrane CLI to discover connectors, create connections, run actions, or proxy requests to the Gigalixir API. Using Membrane as an integration layer is a reasonable design choice for this purpose.
Instruction Scope
SKILL.md instructs the agent/user to install and run the Membrane CLI, perform an interactive login (browser-based or headless flow), list/connect actions, run actions, or proxy raw requests. These instructions stay within the stated purpose but they mean user data and authentication are routed through Membrane's service — the SKILL.md explicitly relies on Membrane to handle auth and to proxy requests.
Install Mechanism
No install spec in registry, but SKILL.md tells the user to run 'npm install -g @membranehq/cli' (and suggests npx in examples). Global npm installs and npx execution pull code from the npm registry; this is common for CLIs but carries the usual supply-chain considerations (verify package source/signature and use pinned versions where appropriate).
Credentials
The skill requests no environment variables or local credentials; authentication is delegated to Membrane's OAuth/browser flow. This is proportionate to the described function.
Persistence & Privilege
The skill is instruction-only, has no install script in registry, and is not marked always:true. It does not request system-level persistence or modify other skills' configs.
Assessment
This skill delegates Gigalixir access to the Membrane service and CLI. Before installing or using it: (1) confirm you trust Membrane (getmembrane.com/@membranehq package and repository) because requests, API parameters, and credentials will transit Membrane's systems; (2) prefer installing a known/pinned CLI version rather than repeatedly running npx@latest; (3) review the Membrane CLI package source on npm/GitHub and validate its reputation; (4) in headless or shared environments, avoid pasting one-time codes into untrusted prompts and verify browser redirect URLs during the login flow; (5) if you need strict data locality or direct Gigalixir access, consider integrating directly with Gigalixir APIs instead of using a proxy.Like a lobster shell, security has layers — review code before you run it.
latestvk974qfmbteqmwv5m4f22fefmmx84esf6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.