prepare-for-confighub SKILL.md skillA
prepare-for-confighub 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/prepare-for-confighub@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/prepare-for-confighub/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260926.4c4b67c, committed Sep 26, 2026
- First version recorded
- May 22, 2026
- Size
- 13,847 bytes
- Repository stars
- 14
- License
- MIT
Use when the user is ADOPTING ConfigHub — they have existing live K8s + GitOps state (an existing cluster, live Argo ApplicationSets, Flux Kustomizations, or secondarily a git repo of manifests) and want to PREVIEW what a ConfigHub import would look like before committing. Natural phrasing: "show me the proposed units before I apply", "I want to adopt ConfigHub for this app", "what would ConfigHub see in our cluster?", "what would ConfigHub see in our argocd setup?…
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
# prepare-for-confighub
The adoption-preview loop. The user has existing live K8s + GitOps state and wants to KNOW what a ConfigHub import would produce **before** committing. Start from the live cluster when possible; use local repo parsing only when the manifest repository itself is under review. This skill is the **preview** flow — every verb is read-only, and `import apply` (the mutating write) is **explicitly out of band**. The user runs that themselves after reviewing the proposal.
## When to use
Explicit phrasings:
- "Show me the proposed units before I apply"
- "I want to adopt ConfigHub for this app — what would it look like?"
- "What would ConfigHub see in this live cluster?"
- "What would ConfigHub see in our Argo CD setup?"
- "Preview what would land in ConfigHub if I imported this repo"
- "Walk me through ConfigHub adoption for `payments-api`"
- "Compare ApplicationSet generator import vs a raw `--git-path` import for this repo"
Implicit intents:
- The user is **before** ConfigHub adoption, not in steady state
- The user wants **reviewable** output, not a live mutation
- The user is comparing options ("what if I use ApplicationSet vs raw YAML import?")
…Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/prepare-for-confighub@sha256:a398ad3baaf6963bThe 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_dpdoxyzdocl6snom)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 22, 2026 and Sep 26, 2026, about one every 32 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.4c4b67c latest | 2026-09-26 | 4c4b67c | 13,847 B | A | view · diff |
| git:20260918.063559f | 2026-09-18 | 063559f | 13,647 B | A | view · diff |
| git:20260528.166d74f | 2026-05-28 | 166d74f | 13,295 B | A | view · diff |
| git:20260522.8abb9be | 2026-05-22 | 8abb9be | 12,803 B | A | view · diff |
| git:20260522.095dc05 | 2026-05-22 | 095dc05 | 12,102 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 (13847 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_dpdoxyzdocl6snom GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/prepare-for-confighub GET https://markdownregistry.com/api/v1/blob/a398ad3baaf6963bf531c33fa981de6b277f9e48476852b9c4b89a2d77c49f48
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.