Rancher Labs

Rancher Labs integration. Manage data, records, and automate workflows. Use when the user wants to interact with Rancher Labs data.

This skill appears to be what it says: a Rancher integration mediated by the Membrane service and CLI. Before installing or using it: 1) Verify @membranehq/cli on npm (author, recent versions, and reputation) or prefer running via npx instead of a global install. 2) Review Membrane's privacy and access model and the GitHub repo (https://github.com/membranedev/application-skills) to ensure you're comfortable giving Membrane a connection to your Rancher environment. 3) When creating connections, grant the minimum Rancher RBAC permissions needed; avoid connecting production clusters with broad tokens. 4) Note the small metadata inconsistency (registry said no binaries required but SKILL.md requires a CLI); treat the CLI requirement as real. If you need higher assurance, request the skill author to add an explicit install spec and declare the membrane CLI as a required binary in the skill metadata, and/or audit the Membrane CLI package code before installing.

Type: OpenClaw Skill Name: rancher-labs Version: 1.0.3 The skill facilitates Rancher Labs management by requiring the installation of a third-party CLI (@membranehq/cli) and routing infrastructure management through an external platform (getmembrane.com). While the instructions in SKILL.md include security best practices—such as avoiding direct secret handling—the requirement for global npm installation and the ability to dynamically create and execute actions via a third-party service constitute high-risk capabilities. These behaviors are plausibly needed for the stated purpose but introduce significant supply chain and infrastructure access risks.