Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Kubernetes Skills
v1.0.0Browser automation for Kubernetes dashboards and web UIs. Use when interacting with Kubernetes Dashboard, Grafana, ArgoCD UI, or other web interfaces. Requires MCP_BROWSER_ENABLED=true.
⭐ 0· 2.4k·4 current·4 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to be a browser automation helper for Kubernetes dashboards, which aligns with the instructions. However the description and SKILL.md say MCP_BROWSER_ENABLED must be set and reference optional provider credentials (MCP_BROWSER_PROVIDER, BROWSERBASE_API_KEY), but the registry metadata lists no required environment variables. That mismatch (declared 'none' vs. instructions requiring env flags/keys) is incoherent and unexplained. Also the skill has no source/homepage, reducing transparency.
Instruction Scope
SKILL.md contains explicit runtime commands for opening arbitrary URLs, attaching Authorization headers, taking screenshots, and retrieving page content. Those are within the stated purpose, but they allow collection and export of potentially sensitive cluster/dashboard data and credentials (the examples even show filling login forms and using bearer tokens). The instructions do not constrain network destinations or explain whether captured screenshots/content remain local or are sent to an external provider, which is a scope and data-exfiltration risk.
Install Mechanism
This is an instruction-only skill with no install spec and no code files — minimal disk footprint. That lowers risk compared to arbitrary downloads. However SKILL.md references external browser provider services (browserbase/browseruse) without an install or network-policy description, so it's unclear how those services are contacted or whether they will receive captured data.
Credentials
The SKILL.md asks users to export MCP_BROWSER_ENABLED and optionally MCP_BROWSER_PROVIDER and BROWSERBASE_API_KEY, but the registry lists no required env vars or primary credential. The skill also shows usage of Authorization headers and credentials in examples without declaring or justifying where such secrets should come from or how they are protected. Requesting or using external provider API keys and arbitrary auth headers is disproportionate without clear justification or constraints.
Persistence & Privilege
always is false and there is no install step that modifies agent/system configuration. The skill does not request elevated or permanent presence. Autonomous invocation is allowed (platform default) — combine this with the other concerns when deciding whether to enable auto-invoke.
What to consider before installing
This skill’s behavior (opening arbitrary dashboard URLs, attaching auth headers, taking screenshots, and retrieving page content) is consistent with a browser automation tool, but the SKILL.md references environment variables and external provider API keys that are not declared in the registry metadata and the package has no known source/homepage. Before installing, verify the author/source and ask for: an explicit list of required env vars, where captured screenshots/page content are stored or transmitted, network endpoints contacted (especially for 'browserbase'/'browseruse'), and the exact data retention/usage policy. Avoid supplying real cluster/admin credentials or bearer tokens until you confirm the skill keeps data local or you trust the external provider. If you must test, do so in an isolated environment with non-production credentials and monitor network traffic. Consider disabling autonomous invocation until you can confirm there is no exfiltration to external services.Like a lobster shell, security has layers — review code before you run it.
latestvk97bt62y0k034qt4z9z5rgm3q17zymtq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.