agentmods.dev

sre-k8s-triage

sre-k8s-triage is a skill for Claude Code from jtprogru/bear-skills. It costs 122 tokens per session (1,882 once invoked), scanned A, original, MIT.

A step-by-step guide for diagnosing Kubernetes problems involving Pods, Deployments, Services, or Ingresses. Kubernetes is software for running and managing containerised applications.

In plain words
What is it for?
Use it to investigate statuses such as Pending, CrashLoopBackOff, ImagePullBackOff, OOMKilled, missing Service endpoints, HTTP 5xx errors, or stuck rollouts.
Why use it?
It turns symptoms such as a crashing Pod, missing traffic, or a stuck deployment into targeted checks and possible mitigations.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the bear-skills plugin — 42 skills, 3 commands, 11 agents, 1 hook shipped together

not rated 1repo 24d ago A scan 122 tokens original MIT

Good fit Use it to investigate statuses such as Pending, CrashLoopBackOff, ImagePullBackOff, OOMKilled, missing Service endpoints, HTTP 5xx errors, or stuck rollouts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jtprogru/bear-skills/sre-k8s-triage
View source ↗ jtprogru/bear-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jtprogru/bear-skills --skill sre-k8s-triage
Clone the repo
git clone --depth 1 https://github.com/jtprogru/bear-skills

Made for: Claude Code.

Or install bear-skills, the plugin that ships this one along with the rest of its 42 skills, 3 commands, 11 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sre-k8s-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/jtprogru/bear-skills/sre-k8s-triage/github.svg)](https://agentmods.dev/skills/jtprogru/bear-skills/sre-k8s-triage)
Your own site
<a href="https://agentmods.dev/skills/jtprogru/bear-skills/sre-k8s-triage"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/sre-k8s-triage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sre-k8s-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/jtprogru/bear-skills/sre-k8s-triage"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/sre-k8s-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,882 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00122 $0.01882
Opus 5 $0.00061 $0.00941
Sonnet 5 $0.00024 $0.00376
Haiku 4.5 $0.00012 $0.00188

Measured 11d ago against content hash 66591e7732b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

sre-k8s-triage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

domains/sre/skills/sre-k8s-triage/SKILL.md · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sre-k8s-triage — Диагностика k8s от симптома к причине

Цель: дать структурированный путь от симптома к гипотезе, без бесцельного kubectl-серфинга.

Перед началом — если у пользователя есть домашний runbook на этот сценарий, посмотри его (~/.claude/rules/sre-runbook-template.md — структура общая).

Шаг 0. Зафиксируй симптом

Спроси:

  • ресурс: Pod / Deployment / Service / Ingress
  • namespace, имя
  • статус: kubectl -n <ns> get <res> <name> — что показывает
  • с какого времени, что изменилось

Если симптом размыт («приложение не работает») — попроси конкретику: ошибка пользователя, HTTP-статус, логи.

Шаг 1. Выбери ветку по симптому

Симптом / Status Идти в раздел
Pod: Pending A. Шедулинг
Pod: CrashLoopBackOff B. Падает на старте
Pod: ImagePullBackOff / ErrImagePull C. Образ
Pod: OOMKilled (в kubectl describe Last State) D. Память
Pod: Running, но не отвечает E. Readiness / трафик
Service: нет endpoints F. Селектор
Ingress: 502/503/504 G. Маршрутизация
Deployment: rollout stuck H. Деплой

A. Pod Pending — шедулинг

kubectl -n <ns> describe pod <pod> | tail -20

Смотри секцию Events. Частые причины:

  • Insufficient cpu/memory → нет нод с нужными ресурсами. Решение: понизить requests, скейл нод, проверить kubectl top nodes.
  • 0/N nodes are available: ... untolerated taint → под не толерирует taint. Решение: добавить tolerations или unaint ноду.
  • pod has unbound immediate PersistentVolumeClaims → PVC не provisioned. Проверить StorageClass, провижионер.
  • node(s) didn't match Pod's node affinity/selector → проверить nodeSelector/affinity.

B. CrashLoopBackOff — падает на старте

kubectl -n <ns> logs <pod> --previous --tail=100
kubectl -n <ns> describe pod <pod> | grep -A5 'Last State'

Частые причины:

  • Exit code 1 + ошибка в логах → ошибка приложения (конфиг, миссинг env-vars, БД недоступна).
  • Exit code 137 → OOM, см. раздел D.
  • Exit code 139 (SIGSEGV) → segfault, скорее всего баг в коде или libc-несовместимость.
  • Liveness probe failure → проверь livenessProbe. Часто стартап дольше, чем initialDelaySeconds.

Read the full file on GitHub · 162 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 162 lines · 122 tokens per session scan A 66591e7732b5

Subscribe to this mod's changes

sre-k8s-triage is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 24d ago), licensed MIT. It adds 122 tokens to every session and 1,882 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude CodeContainersDebuggingDevOps and cloudagentopsagentsai-agentsclaude-code-plugin
Related

Other skills, from other repositories

debug

Evidence-before-action diagnosis of failing ML experiments. Probes the system before guessing causes, process list, dmesg, GPU stats, log scrollback, checkpoint state, then states a hypothesis as a hypothesis and runs a smoke before claiming a root cause. Use when the user asks why a run is failing, diverging, OOMing…

fcakyon/phd-skills · 97 tokens

systematic-debugging

A step-by-step method for investigating and fixing software bugs: reproduce the problem, find its root cause, assess what it may affect, fix it, and test again.

ryanzhao1011/workframe · 40 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - reproduce and isolate before changing anything.

andreymudri/claude-teammates · 29 tokens

debugging-and-recovery

Use when something is broken, a test is failing, behavior is wrong, when investigating a production incident, when a user reports a bug, when a feature works locally but not in another environment, or when the system behaves differently than the contract specifies.

aneja5/forge-skills · 56 tokens

performance-audit

Audit a Godot 4.x project for common performance pitfalls — repeated node lookups, process abuse, missing pooling, untyped collections, missing occlusion, heavy fragment shaders. Reports findings with severity and fix.

Simone-Tarantino/godot-superpowers · 48 tokens

Pair Programming

AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…

spencermarx/open-code-review · 61 tokens