observe-kro SKILL.md skillA
observe-kro 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/observe-kro@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/observe-kro/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260926.4c4b67c, committed Sep 26, 2026
- First version recorded
- May 22, 2026
- Size
- 8,986 bytes
- Repository stars
- 14
- License
- MIT
Use when the user wants to observe KRO-managed resources specifically — the controller-specific observer skill for kro (the Kubernetes Resource Orchestrator). Natural phrasing: "is this a kro instance?", "which ResourceGraphDefinition produced this?", "show me kro applyset writes", "what does `kro.run/applyset` mean?", "trace this resource back to the kro instance". kro is a Kubernetes-native resource orchestrator using applysets. Do NOT load for: generic ownership (use scout-observe)…
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
# observe-kro The controller-specific observer skill for **kro** (Kubernetes Resource Orchestrator) — the project at `kro-run/kro`. cub-scout classifies kro-managed resources via labels, annotations, and owner-reference chains, and recognizes three distinct kro writer identities in `metadata.managedFields`. Verified against `pkg/agent/ownership.go` `detectKroOwnership` and `pkg/agent/manager_strings.go` kro constants. ## When to use - "Is this a kro instance?" - "Which ResourceGraphDefinition produced deploy/api?" - "Show me kro applyset writes" - "What does the `kro.run/applyset` manager string mean?" - "Trace this resource back to the kro instance" - "Distinguish a kro Instance from a kro ResourceGraphDefinition" ## Do not load for - Generic ownership detection — [`scout-observe`](../scout-observe/SKILL.md) - Crossplane (similar composition concept, completely different writers) — [`observe-crossplane`](../observe-crossplane/SKILL.md) - Argo / Flux / Helm — their specific skills - Authoring kro CRDs (writing ResourceGraphDefinitions) — out of cub-scout scope ## Detection signals (in `detectKroOwnership`) cub-scout walks three signal sources in order; the first hit wins: …
Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/observe-kro@sha256:d8e6f4dff27e1f25The 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_twkojz5emeq5p3qm)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 22, 2026 and Sep 26, 2026, about one every 64 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.4c4b67c latest | 2026-09-26 | 4c4b67c | 8,986 B | A | view · diff |
| git:20260624.e6ab578 | 2026-06-24 | e6ab578 | 8,781 B | A | view · diff |
| git:20260522.a5d26c6 | 2026-05-22 | a5d26c6 | 8,764 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 (8986 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_twkojz5emeq5p3qm GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/observe-kro GET https://markdownregistry.com/api/v1/blob/d8e6f4dff27e1f2549c5d082b95b3e23e1191089de148a38429aa6af2924c8a9
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.