scout-diagnose SKILL.md skillA
scout-diagnose 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/scout-diagnose@git:20260910.d56245fPins git:20260910.d56245f 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/scout-diagnose/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260910.d56245f, committed Sep 10, 2026
- First version recorded
- May 21, 2026
- Size
- 10,551 bytes
- Repository stars
- 14
- License
- MIT
Use when the user wants cub-scout to INTERPRET what it sees and suggest a next step — the Diagnose verb group. Natural phrasing: "explain this Deployment", "why is this broken?", "what should I do about this?", "is this drift or just slow sync?", "what does this error mean?", "is there a known pattern for this?", "is my GitOps pipeline healthy?", "what events are firing on this Pod?", "give me a suggested remedy for this finding". Load whenever intent is explain / why / what-does-it-mean /…
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
# scout-diagnose
The Diagnose verb group of cub-scout. Five commands that interpret what's in the cluster and produce next-step guidance — without applying any fix.
## When to use
Explicit phrasings:
- "Explain this Deployment" / "what does this resource mean?"
- "Why is my Pod CrashLooping?" / "what's wrong with this StatefulSet?"
- "What should I do about this?" / "give me a remediation"
- "Is this drift, or just controller still syncing?"
- "Is there a known pattern that matches this?"
- "Is my GitOps pipeline healthy?" / "what's the state of Flux / Argo?"
- "Show me the recent events on this resource"
- "Suggest a remedy for this scan finding"
Implicit intents:
- The user has *already seen* something (via [`scout-observe`](../scout-observe/SKILL.md)) and wants to know *why* it looks that way
- The user wants a concrete next command to run, not just facts
- The user wants pattern-matching against known failure modes, not just raw cluster output
## Do not load for
- Pure inventory ("show me what's running") — load [`scout-observe`](../scout-observe/SKILL.md)
- Comparing intended vs running state at the field level — load [`scout-compare`](../scout-compare/SKILL.md)
…Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/scout-diagnose@sha256:1d06ffe2a92b1e06The line at the top of this page pins the label git:20260910.d56245f, 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_dpktmyruz5lj7k7f)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 21, 2026 and Sep 10, 2026, about one every 56 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.d56245f latest | 2026-09-10 | d56245f | 10,551 B | A | view · diff |
| git:20260910.57da20f | 2026-09-10 | 57da20f | 10,244 B | A | view · diff |
| git:20260521.0276793 | 2026-05-21 | 0276793 | 9,776 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 (10551 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_dpktmyruz5lj7k7f GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/scout-diagnose GET https://markdownregistry.com/api/v1/blob/1d06ffe2a92b1e062f9a16556e3d73e3f75236a5cee6338bafa34bf4de37afb7
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.