New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Multi Cloud Architecture

by wshobson in wshobson/agents

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

MITAuto-check passedDevOps & Cloud

Install Multi Cloud Architecture

skills CLI
$ npx skills add wshobson/agents --skill multi-cloud-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wshobson/agents multi-cloud-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/cloud-infrastructure/skills/multi-cloud-architecture .claude/skills/multi-cloud-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
multi-cloud-architecture
GitHub stars
40k
Token cost
~1.4k tokens
SKILL.md length
504 words
Files
3 (incl. references)
Skills in repo
142
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Assessment → Pilot → Migration → …
  • Building multi-cloud systems
  • SKILL.md covers Purpose, When to Use, Cloud Service Comparison and Multi-Cloud Patterns, plus 5 more sections
  • Calls aws

What it does

Multi Cloud Architecture is an agent skill from wshobson/agents. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/multi-cloud-patterns.md` and `references/service-comparison.md`).

It sits in DevOps & Cloud, covering Cloud architecture. It works with Microsoft Azure, Amazon Web Services, Google Cloud and SQL. The repository describes itself as: Multi-harness agentic plugin marketplace for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Google Antigravity, and Pi. The licence is MIT.

When your agent uses it

  • Building multi-cloud systems
  • Avoiding vendor lock-in
  • Leveraging best-of-breed services from multiple providers

Example prompts

  • “/multi-cloud-architecture”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Assessment
  2. Pilot
  3. Migration
  4. Optimization

What it can do on your machine

Read from SKILL.md and the folder at commit 46891e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • aws

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Multi Cloud Architecture loads about 1.4k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 504 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 504 words, ~1,427 tokens.

Download SKILL.mdSave it as .claude/skills/multi-cloud-architecture/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
multi-cloud-architecture
description
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.

Multi-Cloud Architecture

Decision framework and patterns for architecting applications across AWS, Azure, GCP, and OCI.

Purpose

Design cloud-agnostic architectures and make informed decisions about service selection across cloud providers.

When to Use

  • Design multi-cloud strategies
  • Migrate between cloud providers
  • Select cloud services for specific workloads
  • Implement cloud-agnostic architectures
  • Optimize costs across providers

Cloud Service Comparison

Compute Services
AWSAzureGCPOCIUse Case
EC2Virtual MachinesCompute EngineComputeIaaS VMs
ECSContainer InstancesCloud RunContainer InstancesContainers
EKSAKSGKEOKEKubernetes
LambdaFunctionsCloud FunctionsFunctionsServerless
FargateContainer AppsCloud RunContainer InstancesManaged containers
Storage Services
AWSAzureGCPOCIUse Case
S3Blob StorageCloud StorageObject StorageObject storage
EBSManaged DisksPersistent DiskBlock VolumesBlock storage
EFSAzure FilesFilestoreFile StorageFile storage
GlacierArchive StorageArchive StorageArchive StorageCold storage
Database Services
AWSAzureGCPOCIUse Case
RDSSQL DatabaseCloud SQLMySQL HeatWaveManaged SQL
DynamoDBCosmos DBFirestoreNoSQL DatabaseNoSQL
AuroraPostgreSQL/MySQLCloud SpannerAutonomous DatabaseDistributed SQL
ElastiCacheCache for RedisMemorystoreOCI CacheCaching

Reference: See references/service-comparison.md for complete comparison

Multi-Cloud Patterns

Pattern 1: Single Provider with DR
  • Primary workload in one cloud
  • Disaster recovery in another
  • Database replication across clouds
  • Automated failover
Pattern 2: Best-of-Breed
  • Use best service from each provider
  • AI/ML on GCP
  • Enterprise apps on Azure
  • Regulated data platforms on OCI
  • General compute on AWS
Pattern 3: Geographic Distribution
  • Serve users from nearest cloud region
  • Data sovereignty compliance
  • Global load balancing
  • Regional failover
Pattern 4: Cloud-Agnostic Abstraction
  • Kubernetes for compute
  • PostgreSQL for database
  • S3-compatible storage (MinIO)
  • Open source tools

Cloud-Agnostic Architecture

Use Cloud-Native Alternatives
  • Compute: Kubernetes (EKS/AKS/GKE/OKE)
  • Database: PostgreSQL/MySQL (RDS/SQL Database/Cloud SQL/MySQL HeatWave)
  • Message Queue: Apache Kafka or managed streaming (MSK/Event Hubs/Confluent/OCI Streaming)
  • Cache: Redis (ElastiCache/Azure Cache/Memorystore/OCI Cache)
  • Object Storage: S3-compatible API
  • Monitoring: Prometheus/Grafana
  • Service Mesh: Istio/Linkerd
Show full SKILL.md (196 more words)Show less
Abstraction Layers
Application Layer
    ↓
Infrastructure Abstraction (Terraform)
    ↓
Cloud Provider APIs
    ↓
AWS / Azure / GCP / OCI

Cost Comparison

Compute Pricing Factors
  • AWS: On-demand, Reserved, Spot, Savings Plans
  • Azure: Pay-as-you-go, Reserved, Spot
  • GCP: On-demand, Committed use, Preemptible
  • OCI: Pay-as-you-go, annual commitments, burstable/flexible shapes, preemptible instances
Cost Optimization Strategies
  1. Use reserved/committed capacity (30-70% savings)
  2. Leverage spot/preemptible instances
  3. Right-size resources
  4. Use serverless for variable workloads
  5. Optimize data transfer costs
  6. Implement lifecycle policies
  7. Use cost allocation tags
  8. Monitor with cloud cost tools

Reference: See references/multi-cloud-patterns.md

Migration Strategy

Phase 1: Assessment
  • Inventory current infrastructure
  • Identify dependencies
  • Assess cloud compatibility
  • Estimate costs
Phase 2: Pilot
  • Select pilot workload
  • Implement in target cloud
  • Test thoroughly
  • Document learnings
Phase 3: Migration
  • Migrate workloads incrementally
  • Maintain dual-run period
  • Monitor performance
  • Validate functionality
Phase 4: Optimization
  • Right-size resources
  • Implement cloud-native services
  • Optimize costs
  • Enhance security

Best Practices

  1. Use infrastructure as code (Terraform/OpenTofu)
  2. Implement CI/CD pipelines for deployments
  3. Design for failure across clouds
  4. Use managed services when possible
  5. Implement comprehensive monitoring
  6. Automate cost optimization
  7. Follow security best practices
  8. Document cloud-specific configurations
  9. Test disaster recovery procedures
  10. Train teams on multiple clouds
  • terraform-module-library - For IaC implementation
  • cost-optimization - For cost management
  • hybrid-cloud-networking - For connectivity

© wshobson, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/cloud-infrastructure/skills/multi-cloud-architecture of wshobson/agents.

  • SKILL.md
  • references/multi-cloud-patterns.md
  • references/service-comparison.md

Open the folder on GitHubat commit 46891e7

Compare with similar skills

Multi Cloud Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Multi Cloud Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Multi Cloud Architecture this skillwshobson/agents40k—~1.4kAutomated safety check: PassMIT
Multi Cloud ArchitectureHermeticOrmus/LibreUIUX-Claude-Code11110 repos~1.2kAutomated safety check: PassMIT
Dangling DNS Finderanirudhbiyani/findmytakeover180—~1.8kAutomated safety check: PassGPL-3.0
Cloud Architectdavila7/claude-code-templates32k7 repos~1.9kAutomated safety check: PassMIT
Cloud ArchitectJeffallan/claude-skills12k—~1.9kAutomated safety check: PassMIT
Terraform EngineerJeffallan/claude-skills12k—~1.4kAutomated safety check: PassMIT

Similar skills

  • Multi Cloud Architecture

    HermeticOrmus/LibreUIUX-Claude-Code

    Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP.

    111 GitHub starsUsed in 10 repos~1.2k tokens
    DevOps & CloudAuto-check passed

  • Dangling DNS Finder

    anirudhbiyani/findmytakeover

    Detect dangling DNS records and subdomain-takeover risks across a multi-cloud environment by running the bundled findmytakeover tool.

    180 GitHub stars~1.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Cloud Architect

    davila7/claude-code-templates

    Expert cloud architect specializing in AWS/Azure/GCP multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns.

    32k GitHub starsUsed in 7 repos~1.9k tokens
    DevOps & CloudAuto-check passed

  • Cloud Architect

    Jeffallan/claude-skills

    Designs cloud architectures, migration plans, cost optimization recommendations and disaster recovery strategies across AWS, Azure and GCP.

    12k GitHub stars~1.9k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

  • Terraform Engineer

    Jeffallan/claude-skills

    Writes reusable Terraform modules and manages state, providers and environments across AWS, Azure and GCP, with validation, plan review and explicit apply approval.

    12k GitHub stars~1.4k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

  • Performing Cloud Asset Inventory With Cartography

    mukul975/Anthropic-Cybersecurity-Skills

    Run Cartography to sync AWS, GCP, or Azure resources into a Neo4j graph database, mapping relationships such as IAM permission chains, network paths, and cross-account trust.

    34k GitHub stars~1.7k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from wshobson/agents

All 142 skills in this repo

  • Cloud Cost Optimization

    wshobson/agents

    Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 13 repos~1.7k tokens
    Auto-check passed

  • Billing Automation

    wshobson/agents

    Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.

    40k GitHub starsUsed in 12 repos~473 tokens
    Auto-check passed

  • Python Performance Optimization

    wshobson/agents

    Profiles slow Python code with cProfile and memory profilers, then applies targeted fixes for CPU, memory, I/O and query bottlenecks.

    40k GitHub starsUsed in 12 repos~814 tokens
    Auto-check passed

  • Portfolio Risk Metrics

    wshobson/agents

    Covers portfolio risk measurement with VaR, CVaR, Sharpe, Sortino and drawdown, plus guidance on limits, stress tests and tail risk.

    40k GitHub starsUsed in 12 repos~502 tokens
    Auto-check passed

  • DGX Spark Memory and Thermal Ops

    wshobson/agents

    Plans memory headroom, works through out-of-memory failures and watches temperature and power during long ML training jobs on NVIDIA DGX Spark.

    40k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Bats Shell Testing Patterns

    wshobson/agents

    Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.

    40k GitHub starsUsed in 11 repos~1.3k tokens
    Auto-check passed

Works with

Categories

Questions about Multi Cloud Architecture

What does Multi Cloud Architecture do?

Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, GCP, and OCI. Multi Cloud Architecture is an agent skill from wshobson/agents. Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, GCP, and OCI.

When should I use Multi Cloud Architecture?

Multi Cloud Architecture fits situations like: building multi-cloud systems; avoiding vendor lock-in; leveraging best-of-breed services from multiple providers.

How do I install Multi Cloud Architecture in Claude Code?

Run `npx skills add wshobson/agents --skill multi-cloud-architecture -a claude-code`. Or copy the skill folder (plugins/cloud-infrastructure/skills/multi-cloud-architecture in wshobson/agents) into .claude/skills/multi-cloud-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Multi Cloud Architecture in Codex?

Run `npx skills add wshobson/agents --skill multi-cloud-architecture -a codex`. Or copy the skill folder (plugins/cloud-infrastructure/skills/multi-cloud-architecture in wshobson/agents) into .agents/skills/multi-cloud-architecture in your project. Codex loads it when a task matches its description.

Can I use Multi Cloud Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wshobson/agents --skill multi-cloud-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/multi-cloud-architecture, .gemini/skills/multi-cloud-architecture, .github/skills/multi-cloud-architecture and .opencode/skills/multi-cloud-architecture in your project.

What does Multi Cloud Architecture need to run?

Going by SKILL.md and its folder, Multi Cloud Architecture needs the command-line tools its instructions call (aws).

Does Multi Cloud Architecture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Multi Cloud Architecture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Multi Cloud Architecture use?

Multi Cloud Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Multi Cloud Architecture use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 698 tokens, read only when the agent opens those files.

What are the alternatives to Multi Cloud Architecture?

Skills that share tags, products or a category with Multi Cloud Architecture: Multi Cloud Architecture (HermeticOrmus/LibreUIUX-Claude-Code, 111 stars), Dangling DNS Finder (anirudhbiyani/findmytakeover, 180 stars), Cloud Architect (davila7/claude-code-templates, 32k stars) and Cloud Architect (Jeffallan/claude-skills, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Multi Cloud Architecture?

wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,254 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.

Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.