k8s-incident-triage skillA
k8s-incident-triage is agent-read markdown (skill) from initializ/forge: Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Kubernetes Incident Triage Performs read-only triage of Kubernetes workloads and namespaces using `kubectl`. Supports: - Natural language input (human mode) - Structured JSON input (automation mode) This skill NEVER mutates cluster state. --- ## Tool Usage This skill uses `cli_execute` with `kubectl` commands exclusively. NEVER use http_request or web_search to interact with Kubernetes. All cluster operations MUST go through kubectl via the cli_execute tool. --- ## Tool: k8s_triage Diagnose unhealthy Kubernetes workloads, pods, or namespaces. **Output format:** Use markdown tables for pod/workload status summaries. Wrap kubectl output and log excerpts in ```text code blocks. Use ```bash for recommended next-step commands. --- ## Input Modes ### 1) Human Mode (Natural Language) Input is a plain string. Examples: - `triage payments-prod` - `triage deployment payments-api in payments-prod` - `why are pods pending in checkout-prod?` - `investigate crashloop in payments-prod` - `triage pod api-7c9f6d7f86-abcde in payments-prod` - `check rollout of deployment payments-api in prod` Behavior: - Parse namespace, workload, pod, or selector intent. …
Read the whole file at its exact version.
How to install
mdr add initializ/forge/k8s-incident-triage@git:20260304.ef09c7bmdr add initializ/forge/k8s-incident-triage@sha256:bcd28d2708bceeebPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_fb3jnaruz3okqjl3)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260304.ef09c7b latest | 2026-03-04 | ef09c7b | 6,033 B | A | view · diff |
| git:20260301.e624857 | 2026-03-01 | e624857 | 6,020 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6033 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
initializ/forge · 221 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fb3jnaruz3okqjl3 GET https://markdownregistry.com/api/v1/resolve?ref=initializ/forge/k8s-incident-triage GET https://markdownregistry.com/api/v1/blob/bcd28d2708bceeeb5839246555b3c692007566e60d733c0d56e66cbd3668fc6e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.