Claude Skill

sre-incident-responder

Triage incidents like an SRE - correlate logs, metrics, events and traces, find the root cause, propose remediation, and write the postmortem. Uses k8sgpt when available.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_sre-incident-responder-e9c73a3.zip · 1 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/sre-incident-responder
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

SRE Incident Responder

Overview

Diagnose first, mutate last. Establish the blast radius, timeline, and root cause from evidence before touching anything.

Signal sources

Cross-platform (kubectl, k8sgpt, and docker work identically on Linux, macOS, and Windows):

kubectl get events -A --sort-by=.lastTimestamp
kubectl logs <pod> -n <ns> --previous --tail=200
kubectl top pods -n <ns>
k8sgpt analyze --explain            # if k8sgpt is installed
docker logs --tail 200 <container>

Host logs per OS:

journalctl -u <service> --since "1 hour ago"                      # Linux
log show --last 1h --predicate 'process == "<service>"'           # macOS
Get-WinEvent -LogName Application -MaxEvents 100 |
  Where-Object LevelDisplayName -in 'Error','Critical'            # Windows

Also use Grafana/Prometheus MCP servers when configured for dashboards, alert state, and metric queries.

Workflow

  1. Scope: what is broken, since when, for whom. Pin the first bad timestamp.
  2. Correlate across layers: recent deploys/config changes first (most incidents are changes), then resources (OOM, CPU throttling, disk), then dependencies (DB, DNS, upstream APIs), then infra.
  3. State the root cause with the evidence chain, not just the symptom.
  4. Propose remediation in two parts: immediate mitigation (rollback, restart, scale) and durable fix (code/config/capacity).
  5. Apply mitigation only with approval; verify recovery against the original symptom.
  6. Write a short postmortem: timeline, root cause, impact, actions, follow-ups. Save it under ops/incidents/.

Rules

  • Rollbacks and restarts on prod require human-approval.
  • Never delete evidence (logs, crashed pods) before capturing it.
  • If the cause cannot be proven, list the ranked hypotheses and the test for each; do not guess-remediate.
Files (navin)
  • SKILL.md 2.1 KB
    ---
    name: sre-incident-responder
    description: Triage incidents like an SRE - correlate logs, metrics, events and traces, find the root cause, propose remediation, and write the postmortem. Uses k8sgpt when available.
    metadata: {"navin":{"emoji":"🚨","category":"devops"}}
    ---
    
    # SRE Incident Responder
    
    ## Overview
    
    Diagnose first, mutate last. Establish the blast radius, timeline, and root cause from evidence before touching anything.
    
    ## Signal sources
    
    Cross-platform (kubectl, k8sgpt, and docker work identically on Linux, macOS, and Windows):
    
    ```bash
    kubectl get events -A --sort-by=.lastTimestamp
    kubectl logs <pod> -n <ns> --previous --tail=200
    kubectl top pods -n <ns>
    k8sgpt analyze --explain            # if k8sgpt is installed
    docker logs --tail 200 <container>
    ```
    
    Host logs per OS:
    
    ```bash
    journalctl -u <service> --since "1 hour ago"                      # Linux
    log show --last 1h --predicate 'process == "<service>"'           # macOS
    ```
    
    ```powershell
    Get-WinEvent -LogName Application -MaxEvents 100 |
      Where-Object LevelDisplayName -in 'Error','Critical'            # Windows
    ```
    
    Also use Grafana/Prometheus MCP servers when configured for dashboards, alert state, and metric queries.
    
    ## Workflow
    
    1. Scope: what is broken, since when, for whom. Pin the first bad timestamp.
    2. Correlate across layers: recent deploys/config changes first (most incidents are changes), then resources (OOM, CPU throttling, disk), then dependencies (DB, DNS, upstream APIs), then infra.
    3. State the root cause with the evidence chain, not just the symptom.
    4. Propose remediation in two parts: immediate mitigation (rollback, restart, scale) and durable fix (code/config/capacity).
    5. Apply mitigation only with approval; verify recovery against the original symptom.
    6. Write a short postmortem: timeline, root cause, impact, actions, follow-ups. Save it under `ops/incidents/`.
    
    ## Rules
    
    - Rollbacks and restarts on prod require `human-approval`.
    - Never delete evidence (logs, crashed pods) before capturing it.
    - If the cause cannot be proven, list the ranked hypotheses and the test for each; do not guess-remediate.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related