multi-cloud-architecture

Design multi-cloud architectures using a decision framework across AWS, Azure, GCP, and OCI.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/jamesogunsan/prod-eng-skills --skill multi-cloud-architecture-jamesogunsan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-cloud-architecture
Source: https://github.com/jamesogunsan/prod-eng-skills/tree/main/plugins/cloud-infrastructure/skills/multi-cloud-architecture
Command: npx skills add https://github.com/jamesogunsan/prod-eng-skills --skill multi-cloud-architecture-jamesogunsan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, GCP, and OCI. Build cloud-agnostic designs that reduce vendor lock-in and improve portability.

Core Features & Use Cases

  • Decision framework for evaluating compute, storage, networking, and data services across AWS, Azure, GCP, and OCI.
  • Cloud-agnostic patterns and best practices to enable interoperability and easier migration.
  • Guidance for designing, comparing, and migrating workloads across providers with cost considerations.

Quick Start

Draft a cloud-agnostic architecture plan for a given workload across AWS, Azure, GCP, and OCI

Frequently Asked Questions about multi-cloud-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a multi-cloud architecture across AWS, Azure, GCP, and OCI?

Design multi-cloud architectures by applying a decision framework to evaluate and integrate compute, storage, networking, and data services across AWS, Azure, GCP, and OCI. It enforces cloud-agnostic evaluation criteria and interoperability considerations for cross-provider workloads.

What are the best practices for reducing vendor lock-in during cloud migration?

Reduce vendor lock-in by applying cloud-agnostic patterns and best practices that enable interoperability and easier migration. The framework evaluates portability and cost considerations across providers to maintain workload flexibility.

How does cloud comparison work for selecting compute and storage services across providers?

Cloud comparison uses a decision framework to evaluate compute, storage, networking, and data services across AWS, Azure, GCP, and OCI. It targets cloud architects needing provider comparisons and portable patterns for cross-provider workloads.

Can I use cloud-agnostic patterns to migrate existing workloads across multiple providers?

Yes, you can migrate workloads across providers using cloud-agnostic patterns and best practices. The framework provides migration guidance and interoperability considerations to design, compare, and move workloads across vendors with cost considerations.

When should I avoid a multi-cloud architecture for my workloads?

Avoid multi-cloud architectures when workloads require deep provider-specific optimizations that outweigh portability benefits. The decision framework evaluates cloud-agnostic criteria and interoperability considerations to determine if cross-provider designs suit your specific scale and context.