菜单
Diagnose Kubernetes cluster health, Pod failures, node NotReady/resource pressure, service access issues, events, logs, resource usage, and capacity planning. Use for cluster-level or multi-object Kubernetes incidents.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/clcc2019/dsflow --skill k8s-diagnostic命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Calculate incident impact, detection and recovery durations, classify incidents as L0-L3 from service criticality and impact inputs, compute weighted SLA impact and derived availability, and generate post-incident Markdown reports. Use for SLA calculations, incident severity assessment, outage-duration review, availability summaries, postmortems, incident reports, and remediation tracking.
云原生 SRE 值班助理和巡检编排技能。用于基础设施早检、Kubernetes 集群健康检查、Ceph 存储巡检、计算集群巡检、网关故障初筛、异常证据汇总和值班日报生成。触发场景：用户要求早检、巡检、检查集群是否正常、检查 Ceph、检查计算集群、排查网关错误或生成基础设施健康报告。
Create, review, tune, and validate production-grade Prometheus alerting rules and Kubernetes PrometheusRule resources. Use when writing or repairing alert rule YAML, designing PromQL alert expressions, recommending defensible thresholds and for durations, building SLO/error-budget burn-rate alerts, reducing alert noise, standardizing severity/labels/annotations, adding promtool tests, or reviewing an existing Prometheus rule catalog. 用户要求创建、评审或优化 Prometheus 告警规则、PromQL、告警阈值、告警降噪时使用。
基于 SOC 职业分类
正在显示 SKILL.md
| name | k8s-diagnostic |
| description | Diagnose Kubernetes cluster health, Pod failures, node NotReady/resource pressure, service access issues, events, logs, resource usage, and capacity planning. Use for cluster-level or multi-object Kubernetes incidents. |
Use bundled scripts to gather JSON data. The agent performs analysis and recommendations.
# Cluster overview
scripts/get_cluster_overview.sh --cluster prod-cluster
# Node status, all nodes or one node
scripts/get_node_status.sh --cluster prod-cluster
scripts/get_node_status.sh --cluster prod-cluster --node <node>
# Pod status, namespace or one Pod
scripts/get_pod_status.sh --cluster prod-cluster --namespace <ns>
scripts/get_pod_status.sh --cluster prod-cluster --namespace <ns> --pod <pod>
# Events from Loki/event-exporter
scripts/get_events.sh --cluster prod-cluster --namespace <ns> --type Warning --hours 2
Default Prometheus: https://prometheus.example.com.
get_cluster_overview.sh for cluster-level requests.get_node_status.sh when Ready, pressure, capacity, or scheduling looks abnormal.get_pod_status.sh for Pending, CrashLoopBackOff, OOMKilled, readiness, or restart issues.False or Unknown is critical.<70% normal, 70-85% warning, >85% critical.0 normal, 1-5 warning, >5 critical.0 normal, 1-3 warning, >3 critical.Running: verify readiness and restart count.Succeeded: normal for Jobs.Pending: check FailedScheduling, PVC, image pull, taints, selectors, affinity.Failed or Unknown: inspect container states, exit codes, events, and logs.ImagePullBackOff, ErrImagePull, CrashLoopBackOff, CreateContainerConfigError, ContainerCreating.0 normal, 1 app error, 137 OOMKilled, 139 segfault, 143 SIGTERM.Ready=False/Unknown: inspect kubelet/container runtime, certificates, network, and node logs.MemoryPressure=True: inspect memory usage, OOM logs, high-memory Pods.DiskPressure=True: inspect filesystem and image/log usage.PIDPressure=True: inspect process count and leaks.NetworkUnavailable=True: inspect CNI and node network logs.# Non-running Pods
kube_pod_status_phase{k8s_cluster="prod-cluster", phase!="Running", phase!="Succeeded"} == 1
# High restart count
kube_pod_container_status_restarts_total{k8s_cluster="prod-cluster"} > 5
# OOMKilled
kube_pod_container_status_last_terminated_reason{k8s_cluster="prod-cluster", reason="OOMKilled"} == 1
# NotReady nodes
kube_node_status_condition{condition="Ready", status="false", k8s_cluster="prod-cluster"} == 1
# Pressure nodes
kube_node_status_condition{condition=~"MemoryPressure|DiskPressure|PIDPressure", status="true", k8s_cluster="prod-cluster"} == 1
# Node CPU, memory, disk
100 - (avg by(instance) (rate(node_cpu_seconds_total{mode="idle", k8s_cluster="prod-cluster"}[5m])) * 100)
(1 - node_memory_MemAvailable_bytes{k8s_cluster="prod-cluster"} / node_memory_MemTotal_bytes{k8s_cluster="prod-cluster"}) * 100
(1 - node_filesystem_avail_bytes{mountpoint="/", k8s_cluster="prod-cluster"} / node_filesystem_size_bytes{mountpoint="/", k8s_cluster="prod-cluster"}) * 100
k8s_cluster:prod-cluster namespace:<ns> pod:<pod> error
k8s_cluster:prod-cluster oom OR "out of memory" OR "killed process"
k8s_cluster:prod-cluster job:kubelet error
k8s_cluster:prod-cluster "image pull" OR "ImagePullBackOff"
k8s_cluster:prod-cluster "connection refused" OR "connection timeout" OR "network unreachable"
prod-cluster: productioncompute-cluster: computetencent-cluster: Tencent Cloudaliyun-cluster: Alibaba CloudRead references/k8s_diagnostics.md for detailed thresholds, metric definitions, and remediation guidance.