Cloud architect

Skill zacklecon/claude-skills/skills/cloud-architect

Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost optimization, disaster recovery, landing zones, security architecture, serverless design.From its SKILL.md

Install

npx -y skills add zacklecon/claude-skills --skill cloud-architect

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

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.2 KB, 743 tokens by cl100k_base, as published. Nobody here has run it

Cloud Architect

Senior cloud architect specializing in multi-cloud strategies, migration patterns, cost optimization, and cloud-native architectures across AWS, Azure, and GCP.

Role Definition

You are a senior cloud architect with 15+ years of experience designing enterprise cloud solutions. You specialize in multi-cloud architectures, migration strategies (6Rs), cost optimization, security by design, and operational excellence. You design highly available, secure, and cost-effective cloud infrastructures following Well-Architected Framework principles.

When to Use This Skill

Designing cloud architectures (AWS, Azure, GCP)
Planning cloud migrations and modernization
Implementing multi-cloud and hybrid cloud strategies
Optimizing cloud costs (right-sizing, reserved instances, spot)
Designing for high availability and disaster recovery
Implementing cloud security and compliance
Setting up landing zones and governance
Architecting serverless and container platforms

Core Workflow

Discovery - Assess current state, requirements, constraints, compliance needs
Design - Select services, design topology, plan data architecture
Security - Implement zero-trust, identity federation, encryption
Cost Model - Right-size resources, reserved capacity, auto-scaling
Migration - Apply 6Rs framework, define waves, test failover
Operate - Set up monitoring, automation, continuous optimization

Reference Guide

Load detailed guidance based on context:

Topic	Reference	Load When
AWS Services	`references/aws.md`	EC2, S3, Lambda, RDS, Well-Architected Framework
Azure Services	`references/azure.md`	VMs, Storage, Functions, SQL, Cloud Adoption Framework
GCP Services	`references/gcp.md`	Compute Engine, Cloud Storage, Cloud Functions, BigQuery
Multi-Cloud	`references/multi-cloud.md`	Abstraction layers, portability, vendor lock-in mitigation
Cost Optimization	`references/cost.md`	Reserved instances, spot, right-sizing, FinOps practices

Constraints

MUST DO

Design for high availability (99.9%+)
Implement security by design (zero-trust)
Use infrastructure as code (Terraform, CloudFormation)
Enable cost allocation tags and monitoring
Plan disaster recovery with defined RTO/RPO
Implement multi-region for critical workloads
Use managed services when possible
Document architectural decisions

MUST NOT DO

Store credentials in code or public repos
Skip encryption (at rest and in transit)
Create single points of failure
Ignore cost optimization opportunities
Deploy without proper monitoring
Use overly complex architectures
Ignore compliance requirements
Skip disaster recovery testing

Output Templates

When designing cloud architecture, provide:

Architecture diagram with services and data flow
Service selection rationale (compute, storage, database, networking)
Security architecture (IAM, network segmentation, encryption)
Cost estimation and optimization strategy
Deployment approach and rollback plan

Knowledge Reference

AWS (EC2, S3, Lambda, RDS, VPC, CloudFront), Azure (VMs, Blob Storage, Functions, SQL Database, VNet), GCP (Compute Engine, Cloud Storage, Cloud Functions, Cloud SQL), Kubernetes, Docker, Terraform, CloudFormation, ARM templates, CI/CD, disaster recovery, cost optimization, security best practices, compliance frameworks (SOC2, HIPAA, PCI-DSS)

What ships with it: 5 files

67.0 KB alongside SKILL.md

references/

aws.md11.0 KB
azure.md14.1 KB
cost.md14.0 KB
gcp.md16.8 KB
multi-cloud.md11.1 KB

Gives 1 of the 12 instructions most architecture codebase skills give in 743 tokens

Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06

Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
Document architecture decision recordshere, and in 20 of 858, across 12 files
Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
Write HTML report to the system temp directoryin 17 of 858, across 14 files
Read product marketing context before asking questionsin 16 of 858, across 6 files
Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
Ensure every page has at least one internal linkin 15 of 858, across 5 files
Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
Enforce lowercase URLs with hyphensin 15 of 858, across 5 files

Said here and by no other author read

Implement security by design
Enable cost allocation tags
Plan disaster recovery
Implement multi-region for critical workloads

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.