Mendix
v1.0.2Mendix integration. Manage data, records, and automate workflows. Use when the user wants to interact with Mendix data.
⭐ 0· 75·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 name/description say Mendix integration and the SKILL.md consistently instructs using the Membrane CLI to connect to Mendix, discover actions, run them, or proxy API requests. Required capabilities (network + Membrane account) match the stated purpose.
Instruction Scope
Instructions are limited to installing and using the @membranehq/cli, logging in, creating Membrane connections, listing actions, running actions, and proxying requests. This is within scope. Note: proxying sends requests through Membrane's servers, so any Mendix data or API calls will transit/possibly be stored by that third party — an operational/privacy consideration but not an internal inconsistency.
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to run `npm install -g @membranehq/cli`. Asking users to install a global npm CLI is reasonable for the described workflow, but installing third-party packages globally has the usual supply-chain/trust implications.
Credentials
The skill declares no required environment variables or credentials. It relies on Membrane to manage authentication, which aligns with the instructions (the SKILL.md repeatedly says to create connections rather than provide API keys). No unexplained secrets or unrelated credentials are requested.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide configuration changes. It’s an instruction-only skill and does not request persistent privileges beyond using the Membrane CLI the user installs.
Assessment
This skill is coherent: it delegates Mendix access to the Membrane service and asks you to install the Membrane CLI. Before installing or using it, verify that you trust Membrane (review getmembrane.com, the npm package @membranehq/cli and the referenced GitHub repo), because API calls and data will transit their service. Prefer installing the CLI from the official npm package page, avoid installing unknown packages globally without review, and confirm your organization's policy about routing app data through third-party proxies. If you need to keep all data in-house, consider a direct Mendix integration instead.Like a lobster shell, security has layers — review code before you run it.
latestvk97dmxtdypycqskjqsrynfafph843h1p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.