migrate-from-kubectl SKILL.md skillA
migrate-from-kubectl 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/migrate-from-kubectl@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/migrate-from-kubectl/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260926.4c4b67c, committed Sep 26, 2026
- First version recorded
- May 22, 2026
- Size
- 14,110 bytes
- Repository stars
- 14
- License
- MIT
Use when the user is MIGRATING from ad-hoc `kubectl apply` toward GitOps (Argo / Flux / ConfigHub) — and needs to find the manual edits, decide what to do with each (revert / port to git / accept as canonical), and plan the transition. Natural phrasing: "find all the manual edits in this cluster", "we have years of kubectl-apply, help us move to GitOps", "which resources have been hand-edited?", "audit drift caused by humans not controllers", "port my cluster state to git…
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
# migrate-from-kubectl The legacy-cluster migration loop. A cluster has accumulated `kubectl apply -f` over years; the team wants to adopt GitOps (Argo / Flux / ConfigHub). Step 1 of that migration is **finding what's been hand-touched** and deciding per-resource: revert, port to git, or accept as canonical. This skill composes the attribution layer (`cause: manual-edit`), `map orphans`, `scan`, and `snapshot` / `import --git-path` preview once a repo skeleton exists. Read-only throughout — the actual migration is user-driven. ## When to use Explicit phrasings: - "Find all the manual edits in this cluster" - "We have years of kubectl-apply, help us move to GitOps" - "Which resources have been hand-edited?" - "Audit drift caused by humans (not controllers)" - "Port my cluster state to git" / "scaffold ConfigHub for our legacy cluster" - "Show me everything `kubectl-*` has touched" - "Triage the migration backlog — which resources to handle first?" Implicit intents: - The user is **before** GitOps adoption (no Argo/Flux/ConfigHub for most resources yet) - The user wants a **per-resource plan** (revert / port / accept), not a single fix …
Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/migrate-from-kubectl@sha256:ed55fc19e0dd5905The 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_c7d2qtau73xufnzo)
2 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 | 14,110 B | A | view · diff |
| git:20260528.166d74f | 2026-05-28 | 166d74f | 14,005 B | A | view · diff |
| git:20260522.095dc05 | 2026-05-22 | 095dc05 | 13,979 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 (14110 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_c7d2qtau73xufnzo GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/migrate-from-kubectl GET https://markdownregistry.com/api/v1/blob/ed55fc19e0dd5905cd7318171aa25306ae68cfa4308445f2141df453d9ee6a8f
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.