# Design Resilient Hybrid Cloud Architectures

Hybrid environments create difficult choices across platforms, networks, security, compliance, cost, and operations. This skill structures those choices into practical architecture plans and validation steps.

## Install

```bash
npx skillstore add sickn33/hybrid-cloud-architect
```

## Metadata

- Status: approved
- Slug: sickn33-hybrid-cloud-architect
- Skillstore revision: r2
- Version status: missing
- Tree hash: 9c56761ae55ee18d88186c9ffbdf9c3b24c757c6cc18256276926b5ecaec3b2e
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/hybrid-cloud-architect
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-hybrid-cloud-architect
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-hybrid-cloud-architect/manifest

## Capabilities

- Compares workload placement across AWS, Azure, Google Cloud, OpenStack, VMware, Kubernetes, and edge environments.
- Designs hybrid connectivity using dedicated links, VPNs, SD-WAN, DNS, routing, segmentation, and global load balancing.
- Plans identity federation, zero-trust controls, encryption, key management, compliance mapping, and security monitoring.
- Develops migration, disaster recovery, backup, failover, observability, and business continuity approaches.
- Evaluates infrastructure automation, configuration management, GitOps, policy as code, FinOps, TCO, and capacity planning.

## Use Cases

- Plan an enterprise migration: Create phased workload placement, connectivity, security, rollback, and operating plans for moving on-premises systems into a hybrid cloud.
- Build a compliant platform: Map data, identity, encryption, monitoring, and recovery requirements across public and private cloud environments.
- Control multi-cloud costs: Compare TCO, right-sizing, reserved capacity, chargeback, and performance tradeoffs across heterogeneous infrastructure.

## Prompt Templates

### Outline a hybrid architecture

```
Outline a hybrid architecture for [workload] across [environments]. Identify required inputs, major components, connectivity, security controls, risks, and validation steps.
```

### Place workloads across environments

```
Recommend placement for [workloads] across [platforms]. Compare latency, data gravity, compliance, availability, operational skills, cost, and vendor dependency.
```

### Plan migration and recovery

```
Create a phased migration and disaster recovery plan for [current environment] and [target platforms]. Include dependencies, RTO, RPO, testing, rollback, and ownership.
```

### Review a multi-cloud design

```
Review this hybrid architecture: [design summary]. Identify failure modes, trust boundaries, compliance gaps, cost drivers, observability gaps, and prioritized remediations with verification criteria.
```

## Limitations

- It provides architecture guidance, not deployed infrastructure or tested configuration.
- Recommendations require validation against current provider services, pricing, quotas, and regional availability.
- Compliance guidance does not replace legal review, formal assessment, or organization-specific control testing.
- The referenced implementation playbook is not included in the published file structure.

## Best Practices

- Provide workload inventory, dependencies, data classifications, compliance obligations, service objectives, budget constraints, and current operating capabilities.
- Require explicit assumptions, decision criteria, alternatives, risks, owners, and validation steps in every architecture recommendation.
- Test connectivity, failover, recovery, security controls, observability, and cost assumptions before production adoption.

## Anti Patterns

- Do not select platforms before documenting workload, data, latency, compliance, resilience, and operational requirements.
- Do not treat every cloud as identical or force unnecessary portability across provider-specific services.
- Do not accept architecture guidance as production approval without provider checks, testing, security review, and accountable owners.

## Security Audit

- Audited at: 2026-07-24T00:37:59.149\+00:00
- Summary: All 33 static findings are false positives. Markdown backticks identify a referenced path, while ransomware and reconnaissance matches describe defensive hybrid-cloud architecture topics. No executable code, malicious intent, exfiltration, prompt injection, or reconnaissance workflow was found.

## Stats

- Views: 138
- Downloads: 12
- Favorites: 0
- Popularity score: 0