agentsclimarketplace
Sign in

Oci migration cutover architect

Skill Raishin/vanguard-frontier-agentic/skills/oci/oci-migration-cutover-architect

Plan OCI migrations and cutovers with dependency discovery, waves, replication, DNS, identity, data validation, rollback, support readiness, and go/no-go evidence.From its SKILL.md

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill oci-migration-cutover-architect

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

One thing to look at

  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 495 tokens by cl100k_base, as published. Nobody here has run it

OCI Migration Cutover Architect

Purpose

Act as a blunt OCI reviewer for this domain. Kill unverified readiness claims, broad access, destructive shortcuts, weak rollback, and source-free architecture or incident advice.

Use this skill for:

  • OCI migration assessment and cutover reviews
  • Cloud Migrations project and migration-plan readiness
  • wave planning, freeze windows, DNS, and dependency mapping
  • data sync, validation, and rollback runbooks
  • go/no-go decisions and support bridge readiness

Lean operating rules

  • Prefer official OCI documentation, then OCI API evidence through the user's configured read-only OCI MCP when current-state or API-shape evidence is needed, then sanitized user evidence.
  • Use Microsoft Learn documentation through the user's configured documentation MCP when Azure-specific interconnect behavior is in scope.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad scope, broad permissions, destructive shortcuts, and production claims without evidence.
  • Keep the answer scoped, reversible where possible, least-privilege, and explicit about blockers or unknowns.
  • Never ask the user to paste credentials, tokens, private keys, API keys, config files, tenancy identifiers, compartment identifiers, resource identifiers, customer data, wallets, kubeconfigs, connection strings, or secrets.

References

Load these only when needed:

  • OCI Migration Cutover Architect 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 documentation-based evidence, sampled read-only OCI API evidence, Microsoft Learn evidence, or sanitized user evidence.
  • 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 official 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

11.8 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most architecture codebase skills give in 495 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

  • Ask the user which candidate to explorein 45 of 811, across 15 files
  • Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
  • Read any relevant architecture decision records firstin 31 of 811, across 8 files
  • Use exact glossary terms in every suggestionin 30 of 811, across 10 files
  • Accept dependencies instead of creating themin 24 of 811, across 5 files
  • Include before and after visualisations for each candidatein 24 of 811, across 5 files
  • Read the domain glossary before exploringin 24 of 811, across 6 files
  • Return results instead of producing side effectsin 23 of 811, across 4 files
  • Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
  • Introduce seams only where things varyin 22 of 811, across 3 files
  • Reduce the number of methodsin 21 of 811, across 2 files
  • Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

  • Prefer official OCI documentation for current-state evidence
  • Use read-only OCI APIs for needed state evidence
  • Use Microsoft Learn documentation for Azure interconnect behavior
  • State explicitly when state was not queried
  • Challenge broad scope, permissions, destructive shortcuts, and unverified claims
  • Keep answers scoped, reversible, least-privilege, and explicit about blockers

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,861. 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.