Geored Sre Skill
- 1 repo stars
- Updated November 10, 2025
- geored/sre-skill
geored-sre-skill is a Claude Code plugin that guides systematic, read-only Kubernetes incident investigation and root cause analysis.
About
geored-sre-skill is a Claude Code plugin that teaches a systematic, read-only Kubernetes incident investigation flow aligned with SRE practice. developers and small teams shipping on K8s install it when an outage or flaky rollout forces fast, evidence-based answers instead of ad-hoc kubectl spelunking. The skill emphasizes correlation across logs, events, and metrics, walks common pod and network failure modes, and pushes toward root cause before suggesting fixes. It fits anyone who owns cluster health but does not want the agent to mutate production blindly. Use it during active incidents, post-mortem prep, or when mentoring an agent through a structured 5-phase checklist. Complexity is intermediate: you should already know basic kubectl and pod lifecycle concepts. The outcome is a documented chain of evidence, likely cause, and next remediation steps you can execute or ticket.
- Five-phase investigation methodology correlating logs, events, and metrics read-only via kubectl
- Common failure pattern library for pod, network, and resource incidents
- Multi-source triage distinguishing symptoms from underlying causes
- Actionable remediation recommendations without inventing cluster state
- Structured SRE workflow for Kubernetes service degradation
Geored Sre Skill by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install geored-sre-skill@geored/sre-skillAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | November 10, 2025 |
| Repository | geored/sre-skill ↗ |
What it does
Run structured Kubernetes incident triage in Claude Code when pods crash, degrade, or fail health checks instead of guessing from a single log line.
Who is it for?
Best when you're running Kubernetes and want Claude to follow an SRE-style triage script during live incidents.
Skip if: Skip if you do not run Kubernetes or need automated remediation agents with write access to the cluster.
What you get
After invoking the skill, you get a structured incident narrative, correlated evidence, and prioritized remediation ideas grounded in what you actually observed.
- Structured 5-phase incident investigation narrative
- Symptom versus root-cause distinction with evidence citations
- Prioritized remediation and follow-up checks
By the numbers
- Single-plugin bundle from repository geored/sre-skill
- Investigation flow organized as a 5-phase methodology
- Read-only kubectl-oriented workflow (no cluster mutation by default)
Recommended Plugins
Ahmedasmar Devops Claude SkillsA Claude Code Skills Marketplace for DevOps workflows189
Akin Ozer Cc Devops SkillsA practical skill pack for DevOps work in Claude Code and Codex.281
Antonbabenko Terraform SkillThe Claude Agent Skill for Terraform and OpenTofu - testing, modules, CI/CD, and production patterns2.2k
Aws Samples Aws Emr Utilities1 plugin45
Awudevelop Claude PluginsProduction-ready Claude Code plugins for workflow automation and productivity
Axiomhq CliThe power of Axiom on the command line.59How it compares
Incident methodology skill for kubectl triage, not a monitoring MCP or a deploy pipeline plugin.
FAQ
Who is Geored Sre Skill for?
Developers who operate their own Kubernetes workloads and want Claude Code to investigate outages using logs, events, and metrics in a fixed multi-phase workflow.
When should I use Geored Sre Skill?
Use it when pods fail health checks, crash loop, cannot pull images, hit OOM, or show network issues and you need root cause analysis before changing the cluster.
How do I add Geored Sre Skill to my agent?
Install the geored/sre-skill Claude Code plugin from the registry, ensure kubectl context points at the target cluster, then invoke the skill with a concise incident summary and namespace scope.