multi-cloud-architecture Skill (wshobson) for Claude: What It Does and How to Install It

Gives Claude a decision framework for choosing and combining services across AWS, Azure, GCP and OCI.

Installs: 10.9K; on skills.sh
Stars: 42.1K; on GitHub
Files: 2; besides SKILL.md
Updated: Oct 2026; last repo commit

This skill is a reference guide from wshobson's agents collection. It compares compute, storage and database services across AWS, Azure, GCP and OCI, and describes four multi-cloud patterns: single provider with disaster recovery, best-of-breed, geographic distribution and a cloud-agnostic layer.

It also covers portable building blocks, cost factors, a four-phase migration plan and ten best practices. Two reference files hold a longer service comparison and pattern notes. It loads when you design multi-cloud systems, avoid vendor lock-in or pick services for a workload.

Good for

Architects choosing services across AWS, Azure, GCP and OCI
Teams migrating workloads between cloud providers
Engineers weighing vendor lock-in against managed services
Anyone comparing cost levers across clouds

Install multi-cloud-architecture

Claude Code

Copy this prompt.

Install the multi-cloud-architecture skill in Claude Code. Run this command:

/plugin marketplace add wshobson/agents
/plugin install cloud-infrastructure@claude-code-workflows

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The plugin routes install the whole cloud-infrastructure plugin: 7 agents, 0 commands and 8 skills (counted from the plugin folder in the repo tree, which has no hooks or MCP config files). The skills-only routes install just this skill, with no agents or commands. The skill is a reference guide with no setup of its own.

From the project README. Source.

What's in the skill

When it loads

Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, GCP, and OCI. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.

Sections in SKILL.md

Purpose
When to Use
Cloud Service Comparison
Compute Services
Storage Services
Database Services
Multi-Cloud Patterns
Pattern 1: Single Provider with DR
Pattern 2: Best-of-Breed
Pattern 3: Geographic Distribution
Pattern 4: Cloud-Agnostic Abstraction
Cloud-Agnostic Architecture
Use Cloud-Native Alternatives
Abstraction Layers
Cost Comparison
Compute Pricing Factors

Key facts

Author: wshobson (repo owner)
License: MIT
Installs on skills.sh: 10,897 (Nov 2, 2026)
GitHub stars: 42,081 for the whole wshobson/agents repo (Nov 2, 2026)
Last repo commit: Oct 30, 2026
What it includes: 3 files including SKILL.md: references/multi-cloud-patterns.md and references/service-comparison.md (no scripts)
Part of: The cloud-infrastructure plugin (version 1.3.3) in wshobson/agents. Counted from the plugin folder: 7 agents, 0 commands and 8 skills
Works in: Claude Code, Codex CLI, Cursor, OpenCode, Antigravity CLI, GitHub Copilot and Pi, per the README. Skills-only installers ask which tool you use

What it includes

Compute, storage and database services across AWS, Azure, GCP and OCI
Tables that map equivalent services, such as EKS, AKS, GKE and OKE for Kubernetes. references/service-comparison.md adds streaming.
Read · Service comparison
DR pairing, best-of-breed, geographic split, cloud-agnostic layer
Single provider with disaster recovery elsewhere, best service from each provider, serving users from the nearest cloud, and a portable layer on Kubernetes and PostgreSQL.
Read · Four multi-cloud patterns
Portable building blocks and an abstraction-layer diagram
Lists Kubernetes, PostgreSQL or MySQL, Kafka or managed streaming, Redis, S3-compatible storage, Prometheus and Grafana, and Istio or Linkerd.
Read · Cloud-agnostic architecture
Pricing factors per provider and eight savings strategies
Names pricing models for each cloud, such as on-demand, reserved and spot, and lists eight ways to cut cost.
Read · Cost comparison
Four phases: assessment, pilot, migration, optimization
Checklist items for each phase of moving workloads between providers.
Read · Migration strategy
Ten rules, from infrastructure as code to team training
Includes using Terraform or OpenTofu, CI/CD pipelines, designing for failure and testing disaster recovery.
Read · Best practices
Four patterns in references/multi-cloud-patterns.md
Active-active regional split, best-of-breed service mix, primary and DR pairing, and a portable platform baseline.
Read · Pattern notes
Four platform selection notes in references/service-comparison.md
When to prefer provider-native services, when portability matters, when OCI fits, and what to compare before splitting workloads.
Read · Selection notes

From the official docs

Questions

What does the multi-cloud-architecture skill do?

It gives Claude a decision framework for choosing services across AWS, Azure, GCP and OCI. Claude uses it to compare equivalent services, pick a multi-cloud pattern and plan a migration.

How do I install multi-cloud-architecture?

Use the install box at the top of this page. It lists the plugin route and two skills-only commands: npx skills add wshobson/agents --skill multi-cloud-architecture and gh skill install wshobson/agents multi-cloud-architecture (GitHub CLI 2.90 or later), which skip the plugin's agents and commands.

Does it deploy anything or run Terraform?

It does not ship any deployment code: the folder bundles no scripts. It recommends Terraform or OpenTofu as the infrastructure-as-code layer, but writing or applying that code is a separate request.

Does it give current prices?

No. It lists pricing models for each provider, such as on-demand, reserved and spot, plus eight cost strategies. It does not hold price lists.

Which related skills does it point to?

SKILL.md lists terraform-module-library for IaC, cost-optimization for cost management and hybrid-cloud-networking for connectivity. They are separate skills and this one does not require them.

Is this skill from Anthropic?

No. It is in wshobson/agents, a community collection. The skill sits in the cloud-infrastructure plugin there.

Should I install the whole cloud-infrastructure plugin?

Only if you want the rest. The README documents a plugin route for Claude Code and Codex. The plugin folder holds 7 agents, 0 commands and 8 skills (cost-optimization, hybrid-cloud-networking, istio-traffic-management, linkerd-patterns, mtls-configuration, multi-cloud-architecture, service-mesh-observability, terraform-module-library), and the repo tree shows no hooks or MCP config files in it. The install box offers the plugin and skills-only commands.

Does it work in Codex or Cursor?

The README documents Codex CLI as a plugin route and a skills-only install. For Cursor it points to a plugin marketplace and its setup docs, which we did not check, so follow the README there.

Is it safe?

The folder holds SKILL.md and two reference files and bundles no scripts. Its service mappings and patterns are advice, so treat them as a starting point and check them against each provider documentation before you build on them.

Information

updated Nov 2, 2026

Repository: wshobson/agents
Folder: plugins/cloud-infrastructure/skills/multi-cloud-architecture

wshobson/agents skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 5

multi-cloud-architecture SKILL.md · github.com
wshobson/agents README · github.com
cloud-infrastructure plugin.json · github.com
multi-cloud-architecture multi-cloud-patterns.md · github.com
multi-cloud-architecture service-comparison.md · github.com