What problem does it solve? Standing up or debugging a Materialize monitoring stack often fails in confusing ways: pods that will not start, storage that will not attach, config changes that silently do nothing, and teardowns that hang. This Skill routes you to the right troubleshooting documentation and encodes the operational habits that prevent wrong diagnoses. ## Core Features & Use Cases - Symptom-indexed troubleshooting routing: Points you to docs organized by error strings and failure symptoms rather than by component. - Safe cluster targeting: Enforces explicit kubeconfig context naming so install, restart, and delete operations never hit the wrong cluster. - Diagnostic discipline: Covers timeout misdiagnosis, expired cloud credentials, stale metrics assertions, and ConfigMap versus pod-restart verification. - Use Case: A helm upgrade of the monitoring stack times out in CI. Instead of raising the timeout, you inspect events first, capture diagnostics with test/e2e/dump-diagnostics.sh before the kind cluster dies, and find the real cause in the previous container's logs. ## Quick Start Use the deployment-operations skill to diagnose why the monitoring stack pods are not starting after my Helm install.