Kubeshop
v1.0.0Kubeshop (Testkube) integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kubeshop (Testkube) 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 name/description (Kubeshop/Testkube integration) matches the instructions: discovering actions, creating connections, running actions, and proxying requests via the Membrane platform. Required artifacts (a Membrane account and network access) are consistent with that purpose.
Instruction Scope
SKILL.md confines itself to using the Membrane CLI and the Membrane-hosted connector/proxy to call Testkube APIs. It does not instruct reading unrelated files, scanning system config, or exfiltrating environment variables beyond normal CLI auth flows.
Install Mechanism
No registry install spec is provided (skill is instruction-only). Runtime instructions ask the user to install @membranehq/cli via npm (npm install -g), which is a standard public package install; this is expected for a CLI-driven integration but does write to the host system and should be reviewed/trusted by the user.
Credentials
The skill declares no environment variables or credentials in the registry metadata and the instructions use browser-based Membrane login/connection flows rather than asking for API keys or unrelated secrets. This is proportionate to the stated functionality.
Persistence & Privilege
The skill is not forced-always, has no install-time persistence, and does not request changes to other skills or system-wide settings. It relies on the Membrane CLI's runtime auth rather than embedding long-lived credentials.
Assessment
This is an instruction-only skill that expects you to install and use the Membrane CLI and to have a Membrane account. Before installing or running commands: (1) verify you trust getmembrane.com and the @membranehq/cli npm package (review its npm page and source), (2) be aware npm -g writes binaries to your system PATH, and (3) when creating a connector, check what permissions the connector will request for your Kubernetes/Testkube environment — granting broad cluster permissions to third-party services can expose resources. The skill itself does not request unrelated credentials or hidden filesystem access, but the external Membrane service will mediate access to your Testkube APIs, so review its privacy/security docs if that matters.Like a lobster shell, security has layers — review code before you run it.
latestvk97c7m5y7mvpc34k881j3x1471849z23
License
MIT-0
Free to use, modify, and redistribute. No attribution required.