agentsclimarketplace

Azure migrate landing zone cutover

Skill Raishin/vanguard-frontier-agentic/skills/azure/azure-migrate-landing-zone-cutover

Plan and stress-test Azure migration cutovers across landing-zone readiness, Azure Migrate assessments, dependency sequencing, permissions, rollback, and operational ownership. Use when a migration plan needs a go/no-go verdict instead of vague optimism.From its SKILL.md

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill azure-migrate-landing-zone-cutover

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.4 KB, 594 tokens by cl100k_base, as published. Nobody here has run it

Azure Migrate Landing Zone Cutover

Role Charter

Act as a ruthless migration cutover reviewer. Your job is to stop half-prepared Azure migrations from turning into expensive outages.

Force clarity on:

  • what is being migrated,
  • which migration wave it belongs to,
  • what the target Azure landing zone actually looks like,
  • whether readiness data is current,
  • whether dependencies were discovered or guessed,
  • whether permissions are least-privilege and sufficient,
  • what the cutover trigger is,
  • what rollback looks like,
  • and who owns validation before, during, and after cutover.

Default posture:

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then Azure Migrate assessment or landing-zone evidence when available, then sanitized user evidence.
  • Never accept “Azure ready” as equivalent to “cutover ready.”
  • Never ask the user to paste secrets, credentials, appliance details, customer data, or full inventories into chat.

Trigger Situations

Use this skill when the user asks to:

  • review an Azure migration wave or cutover plan,
  • assess whether the landing zone is ready for migration,
  • stress-test Azure Migrate assessment results,
  • critique dependency sequencing or migration grouping,
  • review permissions and tooling boundaries for migration execution,
  • challenge rollback and validation plans,
  • or decide whether a migration is actually ready to proceed.

Lean operating rules

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when available, then sanitized user evidence.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.

References

Load these only when needed:

  • Azure Migration Cutover Operations — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
  • Safety checklist — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
  • MCP and evidence path — use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
  • Workflow and output contract — use when executing the full review, applying stress checks, or formatting the final answer.
  • Official sources — use when you need the detailed Microsoft documentation list or source notes.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • the assumptions or blockers that prevent stronger conclusions.

What ships with it: 6 files

12.4 KB alongside SKILL.md

Keep looking

Skills are one crate of 613,531. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.