Multi-Cloud Strategy Advisor

Design multi-cloud strategies across AWS, Azure, and GCP with vendor scoring and TCO analysis.

6|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill multi-cloud-strategy-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Multi-Cloud Strategy Advisor
Source: https://github.com/williamzujkowski/cognitive-toolworks/tree/main/skills/cloud-multicloud-advisor
Command: npx skills add https://github.com/williamzujkowski/cognitive-toolworks --skill multi-cloud-strategy-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams struggle to evaluate vendors, cost, and architecture across AWS, Azure, and GCP to build portable, cost-aware multi-cloud solutions.

Core Features & Use Cases

  • Vendor comparison matrices, TCO analysis, and architecture patterns for cloud neutrality.
  • Migration roadmaps and lock-in mitigation strategies across providers.
  • Integration patterns (IaC, Kubernetes, service mesh) and identity federation for cross-cloud governance.

Quick Start

Provide your workload requirements and let the system generate a multi-cloud strategy with vendor scores, TCO, and a migration roadmap.

Frequently Asked Questions about Multi-Cloud Strategy Advisor

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

FAQPage Schema
How do I compare AWS, Azure, and GCP for a multi-cloud architecture?

Comparing AWS, Azure, and GCP for a multi-cloud architecture involves evaluating vendor options, architecture patterns, and total cost of ownership. You receive vendor scoring, cost analysis, integration patterns, and a phased migration roadmap to ensure cloud neutrality.

What is the best way to calculate TCO and mitigate vendor lock-in for hybrid cloud deployments?

The best way to calculate TCO and mitigate vendor lock-in for hybrid cloud deployments is by applying portability-focused workload analysis. This generates cost analysis, vendor comparison matrices, and lock-in mitigation strategies across providers.

How does identity federation work for cross-cloud governance across enterprise environments?

Identity federation for cross-cloud governance works by integrating IaC, Kubernetes, and service mesh across providers. It enables unified access control and portability-focused workload management across enterprise environments.

Can I use this approach to design a migration roadmap for data residency constraints?

Yes, you can design a migration roadmap for data residency constraints by evaluating vendor options and architecture patterns. The system generates a phased migration roadmap addressing data residency constraints and portability-focused workloads across enterprise environments.

When should I not use a multi-cloud strategy for my workloads?

You should not use a multi-cloud strategy when workloads lack portability requirements or when integration complexity outweighs vendor lock-in risks. If data residency constraints or hybrid cloud deployments are absent, a single-provider approach may yield better cost efficiency.