Multi Cloud Architecture
CheckedThis skill designs robust, scalable multi-cloud architectures for optimal performance and resilience across diverse environments.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add wshobson/agents --skill multi-cloud-architecture -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
wshobson
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned wshobson/agents at 46891e7e60.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 46891e7e60
- Scanned
- 3 files, 241 lines
About this skill
What it does
This skill assists in designing robust and scalable multi-cloud architectures across AWS, Azure, Google Cloud Platform (GCP), and Oracle Cloud Infrastructure (OCI). It provides a decision framework and service comparison patterns to enable informed choices about cloud services and reduce vendor lock-in. The skill focuses on identifying equivalent offerings and best-of-breed selections for compute, storage, and database workloads.
When to use it
- Designing multi-cloud strategies from the ground up.
- Planning migrations between different cloud providers.
- Selecting appropriate cloud services for specific application workloads.
- Implementing architectures that are not tied to a single cloud vendor.
- Optimizing costs across multiple cloud providers.
Key capabilities
- Detailed service mapping tables comparing offerings across AWS, Azure, GCP, and OCI (compute, storage, database).
- Four core multi-cloud architectural patterns: single provider with disaster recovery, best-of-breed selection, geographic distribution, and cloud-agnostic abstraction layers.
- Identification of cloud-agnostic alternatives using technologies like Kubernetes, PostgreSQL, Apache Kafka, and Redis.
- Cost comparison and optimization strategies including reserved capacity, spot instances, right-sizing, and lifecycle policies.
- Guidance on phased migration strategies from assessment to optimization.
Example prompts
- "Compare the compute services available across AWS, Azure, GCP, and OCI for running containerized applications."
- "What are some options for cloud-agnostic object storage?"
- "Describe a multi-cloud architecture pattern that prioritizes disaster recovery."
Tips & gotchas
- The skill provides guidance on service selection; it's up to the user to evaluate specific requirements and make final decisions.
- Focuses on architectural patterns and comparisons, not implementation details of individual services.
- Consider cloud-agnostic tools like Kubernetes when aiming for portability across providers.