Situation Monitor

Triages Discord activity and Kubernetes incidents into ranked situation reports with fixture-first demos, live Discord and Apify intake, Contextual-grounded...

Before installing or enabling this skill: - Treat it as high-risk until the maintainer clarifies requirements. The published metadata lists only bash and python3, but the repo and docs also require node/npm, kubectl, gcloud, and many sensitive API tokens (Apify, Friendli, Contextual, Redis, Discord). Ask the author to update SKILL metadata to list all required binaries, env vars, and config paths. - Do NOT run demo trigger commands (02-incidents.sh trigger* or destroy) against any real/production cluster. Those scripts intentionally inject failures and can delete a GKE cluster. - If you need to evaluate safely, run the skill in an isolated environment: a disposable hackathon-only cluster and a sandboxed gateway with least-privilege service accounts (KUBECONFIG referencing a limited-access account), and network egress controlled for third-party tokens. - Ensure a formal install step is added (or follow author instructions) that documents npm install for the Apify actor and Python venv creation so dependencies are reproducible and auditable. - Verify who will have access to the listed tokens and whether the OpenClaw host will store them securely; treat REDIS_URL, FRIENDLI_TOKEN, APIFY_TOKEN, CONTEXTUAL_API_KEY, and DISCORD_BOT_TOKEN as sensitive secrets. - If the skill will run in a hosted OpenClaw instance, require an admin review and a configuration checklist: (1) KUBECONFIG points to a non-production, limited account; (2) Node/npm are installed in a controlled environment; (3) required env vars are added intentionally; (4) destructive demo commands are disabled or removed. If the author provides corrected metadata (declare all env vars and binaries), an explicit non-destructive default config, and an install spec for Node, this assessment could move toward 'benign'.

Type: OpenClaw Skill Name: situation-monitor Version: 0.1.2 The skill bundle provides legitimate SRE monitoring and triage functionality but includes high-risk capabilities that warrant a suspicious classification. Specifically, '02-incidents.sh' contains a destructive command to delete a GKE cluster ('gcloud container clusters delete'), and 'src/monitoring_the_situation/cluster_live.py' executes 'kubectl' commands via 'subprocess.run' based on agent-provided arguments. Additionally, 'SKILL.md' contains hardcoded absolute local paths and instructions for the agent to perform 'npm install' and 'node' executions. While these behaviors are plausibly aligned with the stated purpose of Kubernetes monitoring and incident simulation, they represent a high-risk attack surface. No clear evidence of intentional malice or data exfiltration was found, and the inclusion of an 'ApprovalGate' in 'src/monitoring_the_situation/approvals.py' suggests a focus on operational safety.