agentsclimarketplace

Multi cloud architecture

Skill Microck/ordinary-claude-skills/skills_categorized/cicd/multi-cloud-architecture

An unappealing collection of Claude Skills and resources.

Install
npx -y skills add Microck/ordinary-claude-skills --skill multi-cloud-architecture

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

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

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

SKILL.md

4.7 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

Multi-Cloud Architecture

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

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

AWSAzureGCPUse Case
EC2Virtual MachinesCompute EngineIaaS VMs
ECSContainer InstancesCloud RunContainers
EKSAKSGKEKubernetes
LambdaFunctionsCloud FunctionsServerless
FargateContainer AppsCloud RunManaged containers

Storage Services

AWSAzureGCPUse Case
S3Blob StorageCloud StorageObject storage
EBSManaged DisksPersistent DiskBlock storage
EFSAzure FilesFilestoreFile storage
GlacierArchive StorageArchive StorageCold storage

Database Services

AWSAzureGCPUse Case
RDSSQL DatabaseCloud SQLManaged SQL
DynamoDBCosmos DBFirestoreNoSQL
AuroraPostgreSQL/MySQLCloud SpannerDistributed SQL
ElastiCacheCache for RedisMemorystoreCaching

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
  • 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)
  • Database: PostgreSQL/MySQL (RDS/SQL Database/Cloud SQL)
  • Message Queue: Apache Kafka (MSK/Event Hubs/Confluent)
  • Cache: Redis (ElastiCache/Azure Cache/Memorystore)
  • Object Storage: S3-compatible API
  • Monitoring: Prometheus/Grafana
  • Service Mesh: Istio/Linkerd

Abstraction Layers

Application Layer
    ↓
Infrastructure Abstraction (Terraform)
    ↓
Cloud Provider APIs
    ↓
AWS / Azure / GCP

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

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

Reference Files

  • references/service-comparison.md - Complete service comparison
  • references/multi-cloud-patterns.md - Architecture patterns

Related Skills

  • terraform-module-library - For IaC implementation
  • cost-optimization - For cost management
  • hybrid-cloud-networking - For connectivity

Gives 0 of the 12 instructions most architecture codebase skills give in ~1.1k tokens

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

  • ask the user which candidate to explorein 46 of 811, across 16 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 7 files
  • use exact glossary terms in every suggestionin 29 of 811, across 9 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 2 files

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 328,083. 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.