| name | k8s-troubleshooter |
| description | Systematic Kubernetes troubleshooting and incident response. Use this skill whenever the user mentions Kubernetes, K8s, kubectl, pods, containers, or clusters. Triggers include diagnosing CrashLoopBackOff, ImagePullBackOff, OOMKilled, or Pending pods, responding to production incidents, troubleshooting node NotReady or DiskPressure, debugging service connectivity or networking, investigating PVC or storage. |
| source_skill_id | ahmedasmar-devops-claude-skills-k8s-troubleshooter-skills-skill-md |
| category | DevOps, cloud & operations |
| source_mirror | ../../../../../skills/by-category/devops-cloud-operations/devops-reference/k8s-troubleshooter/SKILL.md |
| benchmark_status | artifact_gated |
k8s-troubleshooter
Use this skill when the task matches the description above or the source path clearly applies. Start with this concise entrypoint; open ../../../../../skills/by-category/devops-cloud-operations/devops-reference/k8s-troubleshooter/SKILL.md only when implementation details, commands, assets, or references are needed.
Workflow
- Confirm the task matches this skill's scope.
- Read the local source mirror if more detail is required.
- Follow repository-level
AGENTS.md; use one AI session only.
- Keep claims tied to files, commands, citations, or benchmark artifacts.
Verification
- Source mirror:
../../../../../skills/by-category/devops-cloud-operations/devops-reference/k8s-troubleshooter/SKILL.md
- Source commit:
1489c33ad8829a11219e423327d6b59f8339cee4
- Static benchmark results: see
docs/benchmark-results.md
- Runtime artifacts recorded by this entrypoint:
0
- Assigned scenarios:
skill-proof-ahmedasmar-devops-claude-skills-k8s-troubleshooter-skills-skill-md, devops-cloud-and-operations-kubernetes-examples, devops-cloud-and-operations-opentelemetry-demo, devops-cloud-and-operations-local-omero-compose-workflows
Do not claim this skill passed a runtime benchmark until a validated artifact exists.
