Mlflow
v1.0.0MLflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with MLflow data.
⭐ 0· 29·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 named 'Mlflow' and all runtime instructions show how to interact with MLflow through the Membrane CLI/proxy. Asking the user to install and use the Membrane CLI is consistent with the described integration.
Instruction Scope
SKILL.md limits actions to installing/running the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to MLflow. It does not instruct reading unrelated files or harvesting unrelated environment variables, and it explicitly recommends letting Membrane manage credentials.
Install Mechanism
There is no automated install spec in the skill bundle (instruction-only), but the guide tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a reasonable, common step for a CLI, but it does require pulling code from the public npm registry and elevating a package to global PATH—users should verify the publisher and trustworthiness of the package before installing.
Credentials
The skill declares no required env vars or credentials. It does require a Membrane account (handled via browser login) and network access, which aligns with the described functionality. The documentation explicitly warns not to ask the user for API keys, keeping credential handling proportional and delegated to Membrane.
Persistence & Privilege
The skill is instruction-only, not always-on, and does not request to modify other skills or system-wide agent settings. Default autonomous invocation is allowed (platform default) but is not combined with other concerning privileges.
Assessment
This skill appears to be what it says: a set of instructions to use the Membrane CLI as a proxy to MLflow. Before installing/using it: (1) verify you trust the Membrane project and the npm package publisher (@membranehq) since `npm install -g` will install remote code globally; (2) confirm the Membrane privacy/security posture for storing/refreshing credentials (Membrane will handle your MLflow auth server-side); (3) run CLI commands in a controlled environment (particularly if using headless login or pasting codes); and (4) if you prefer not to install global npm packages, consider running the CLI via npx or in an isolated environment. Overall the skill is coherent, but trust in the third-party Membrane service is the main operational consideration.Like a lobster shell, security has layers — review code before you run it.
latestvk97bc6bsmv4jfsdw5nhynyt2y58478pa
License
MIT-0
Free to use, modify, and redistribute. No attribution required.