Makini
v1.0.0Makini integration. Manage data, records, and automate workflows. Use when the user wants to interact with Makini data.
⭐ 0· 57·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 (Makini integration) matches the instructions: all commands call the Membrane CLI to discover connectors, create connections, run actions, or proxy API requests to Makini. Nothing requested in the skill (no extra env vars, no unrelated binaries) is out of scope for this purpose.
Instruction Scope
SKILL.md limits runtime actions to installing/using the @membranehq/cli, running membrane login, connection/action list/run, and proxying requests via Membrane. It does not instruct reading unrelated files, searching local config, or asking for arbitrary secrets. Browser-based OAuth and headless flow are described and appropriate for this integration.
Install Mechanism
There is no registry install spec; the instructions tell the user to run npm install -g @membranehq/cli (or npx in examples). Installing a global npm package is expected for a CLI-based integration but carries the usual supply-chain and privilege considerations (npm package code will run on the system). Consider using npx, a virtual environment, or auditing the package source before installing globally.
Credentials
The skill declares no required env vars or credentials and explicitly instructs not to ask users for API keys, relying on Membrane's OAuth/connection flow instead. This credential model is proportionate to the stated purpose.
Persistence & Privilege
The skill is instruction-only, has always:false, and does not request persistent privileged presence or modify other skills or system-wide settings. Autonomous invocation is allowed by platform default but not elevated by this skill.
Assessment
This skill is internally consistent: it uses the Membrane CLI to access Makini and does not ask for unrelated secrets. Before installing, consider: (1) prefer using npx or a container rather than npm -g to avoid system-wide installs; (2) review the @membranehq/cli package repository and recent releases to ensure you trust the package; (3) be aware the flow uses browser OAuth and that Membrane's servers will hold connector credentials — review Membrane's privacy/security docs; (4) avoid running CLI commands from this skill on machines with highly sensitive local data unless you trust the Membrane service and the CLI package.Like a lobster shell, security has layers — review code before you run it.
latestvk975wp2rreqq2113t9m9qjc501849ds2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.