triage-unhealthy-workload SKILL.md skillA
triage-unhealthy-workload from confighub/cub-scout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add confighub/cub-scout/triage-unhealthy-workload@git:20260926.4c4b67cPins git:20260926.4c4b67c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- confighub/cub-scout
- Path
skills/triage-unhealthy-workload/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260926.4c4b67c, committed Sep 26, 2026
- First version recorded
- May 22, 2026
- Size
- 10,410 bytes
- Repository stars
- 14
- License
- MIT
Use when the user is responding to a broken Kubernetes workload UNDER TIME PRESSURE — pager-going-off, CI-red, "prod is down" framing. Natural phrasing: "deploy/api is CrashLoopBackOff, what now?", "the rollout is stuck, help", "this pod won''t start", "pager fired on payments", "everything is red in argocd", "what should I check first?", "give me a triage plan for this workload". Composes doctor → explain → trace into a tight ~30-second loop the operator can run in a pager-acknowledged context.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# triage-unhealthy-workload The pager-pressed loop. A workload is broken and the operator has 30 seconds before they need to make a decision. This skill composes `doctor` → `explain` → `trace` (plus targeted `kubectl` reads) into the tightest possible investigation path, with a checklist for what to look at FIRST. ## When to use Explicit phrasings: - "deploy/api is CrashLoopBackOff, what now?" - "The rollout is stuck on `1/3 ready`, help" - "This pod won't start — pager just fired" - "Everything is red in Argo CD" / "Flux Kustomization is in `False` state" - "What should I check first on this workload?" - "Give me a triage plan for `<kind>/<name>`" - "Production is degraded — what does cub-scout see?" Implicit intents: - Time pressure (`now`, `urgent`, `pager`, `prod is down`) - The user wants a *plan*, not a full report — short, ordered, actionable - The user already knows *what* is broken, they need to figure out *why* - The user may need to escalate or roll back; they need evidence first ## Do not load for - A planned investigation without urgency — [`scout-diagnose`](../scout-diagnose/SKILL.md) covers the verb group at leisure …
Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/triage-unhealthy-workload@sha256:a6f24665c95c0e00The line at the top of this page pins the label git:20260926.4c4b67c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6ociii7zn2nglkdl)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 22, 2026 and Sep 26, 2026, about one every 127 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.4c4b67c latest | 2026-09-26 | 4c4b67c | 10,410 B | A | view · diff |
| git:20260522.095dc05 | 2026-05-22 | 095dc05 | 10,205 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 (10410 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
confighub/cub-scout · 14 stars · license MIT · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6ociii7zn2nglkdl GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/triage-unhealthy-workload GET https://markdownregistry.com/api/v1/blob/a6f24665c95c0e0053411602e1af9317309c85dc05b0071bb31cdf53f7191b06
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.