plan-v2-migration SKILL.md skillA
plan-v2-migration from upbound/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add upbound/skills/plan-v2-migration@git:20261012.a0b20d2Pins git:20261012.a0b20d2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- upbound/skills
- Path
skills/plan-v2-migration/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261012.a0b20d2, committed Oct 12, 2026
- First version recorded
- Oct 8, 2026
- Size
- 8,169 bytes
- Repository stars
- 4
- License
- Apache-2.0
Use this skill when user requests to migrate, upgrade, or plan migration to Crossplane v2. Analyzes an existing v1 configuration package and writes a migration plan covering XRD updates, provider API groups, function code changes, test updates, examples and dependencies, with the decisions a migration needs recorded. Use immediately when user mentions "migrate to v2", "upgrade to crossplane v2", "plan v2 migration", or "crossplane 2 migration". Use this skill instead of manually analyzing…
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
# Crossplane v2 migration planner Analyze a Crossplane v1 configuration package and write the plan that `execute-v2-migration` carries out: `.agents/plans/CROSSPLANE_V2_MIGRATION.md`. ## Before you start Load `control-plane-project-charter` first, or read its `SKILL.md` beside this skill's directory; this skill does not load it. The only questions are whether to replace an existing plan (Phase 1) and Phase 5's decisions, asked only when interactive (charter §1). - Analysis only: write the plan file and nothing else — no code changes, builds, tests or commits. - Every change you plan comes from [breaking-changes.md](references/breaking-changes.md). Point at its sections; do not restate them in the plan. Upstream: the [Crossplane v2 upgrade guide](https://docs.crossplane.io/latest/guides/upgrade-to-crossplane-v2/) and [What's new in v2](https://docs.crossplane.io/latest/whats-new/). - The plan changes the project, not a control plane. Moving a control plane that runs the v1 package is a rollout risk you record, never a step you plan ([Installed v1 APIs](references/breaking-changes.md#installed-v1-apis)). ## Phase 1: Confirm a v1 project …
Read the whole file at its exact version.
How to install
mdr add upbound/skills/plan-v2-migration@sha256:feaa54d7412a00caThe line at the top of this page pins the label git:20261012.a0b20d2, 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_qclom5rqsosmxqm2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 8, 2026 and Oct 12, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.a0b20d2 latest | 2026-10-12 | a0b20d2 | 8,169 B | A | view · diff |
| git:20261008.17a6e1f | 2026-10-08 | 17a6e1f | 7,568 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 (8169 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
upbound/skills · 4 stars · license Apache-2.0 · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qclom5rqsosmxqm2 GET https://markdownregistry.com/api/v1/resolve?ref=upbound/skills/plan-v2-migration GET https://markdownregistry.com/api/v1/blob/feaa54d7412a00ca0d7a2f86f370fb97e44cf7127f1350a986fe4baeaf5c91d4
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.