Red Hat
v1.0.0Red Hat integration. Manage data, records, and automate workflows. Use when the user wants to interact with Red Hat data.
⭐ 0· 64·0 current·0 all-time
byMembrane Dev@membranedev
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 claim Red Hat integration and the SKILL.md exclusively documents using the Membrane CLI to connect to Red Hat APIs and run actions. Required capabilities (network, Membrane account, Membrane CLI) match the stated purpose; no unrelated credentials or binaries are requested.
Instruction Scope
Runtime instructions are limited to installing/using @membranehq/cli, logging in, creating connections, listing/running actions, and proxying API requests through Membrane. The instructions do not ask the agent to read local secrets, arbitrary files, or unrelated system config.
Install Mechanism
There is no automated install spec in the package; the README recommends installing a public npm package (npm install -g @membranehq/cli) or using npx. This is a common, low-risk install pattern. Note: global npm installs modify the host environment, so standard caution applies.
Credentials
The skill requests no local env vars and delegates auth to Membrane (browser login / connector flow). This is proportionate to the task, but it does mean the user is delegating access to their Red Hat data to the Membrane service — verifying Membrane's trustworthiness and permissions granted during connector setup is important.
Persistence & Privilege
The skill is instruction-only and not marked always:true. It does not request persistent agent privileges or to modify other skills. The only persistence is the typical installation of a CLI tool if the user chooses to install it.
Assessment
This skill is coherent and appears to do what it says: it uses the Membrane CLI to access Red Hat services. Before installing/using it, verify you trust Membrane (https://getmembrane.com) since the connector flow grants that service access to your Red Hat data; review the permissions shown during the connector/login flow. Prefer using npx for one-off use to avoid a global npm install, and in corporate environments check with your security team before delegating access to an external integration service.Like a lobster shell, security has layers — review code before you run it.
latestvk979z6vz0d6egptwadqzwfdgz584bjp8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.