cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. 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.
98
100%
Does it follow best practices?
Impact
96%
1.14xAverage score across 6 eval scenarios
Passed
No known issues
Evaluation results
100%
AWS Enterprise Landing Zone for a Growing SaaS Company
AWS Landing Zone Design
IaC specified
100%
100%
Control Tower used
100%
100%
Multi-account OUs
100%
100%
Architecture diagram present
100%
100%
Service selection rationale
100%
100%
Security architecture section
100%
100%
Cost estimation included
100%
100%
Deployment/rollback plan
100%
100%
Cost allocation tags
100%
100%
No single points of failure
100%
100%
Managed services preference
100%
100%
Zero-trust / security by design
100%
100%
95%
13%Cloud Migration Plan for Legacy E-Commerce Platform
Cloud Migration Planning with 6Rs
6Rs framework applied
70%
70%
Per-workload 6R classification
80%
100%
RTO/RPO defined
100%
100%
DR pattern named
25%
100%
Multi-region for critical workloads
62%
100%
Monitoring in operate phase
100%
100%
Discovery phase present
62%
75%
IaC for deployment
100%
100%
Architecture diagram/topology
87%
100%
Cost optimization strategy
100%
100%
No single points of failure
100%
100%
Managed services preferred
100%
100%
100%
8%Multi-Cloud Cost Visibility and Efficiency Program
Multi-Cloud FinOps and Observability
FinOps lifecycle referenced
50%
100%
Unified tagging strategy
100%
100%
Required tag keys present
100%
100%
OpenTelemetry for observability
100%
100%
Grafana for unified dashboards
100%
100%
Reserved instance coverage target
62%
100%
Cost waste target
100%
100%
Right-sizing included
100%
100%
Spot/preemptible for batch
100%
100%
Cost allocation reports
100%
100%
IaC for governance
100%
100%
Cost monitoring/alerting
100%
100%
100%
4%Serverless Payments API Architecture
Serverless security hardening and output template completeness
Architecture diagram present
100%
100%
Service selection rationale
100%
100%
Security architecture section
100%
100%
Cost estimation section
100%
100%
Deployment and rollback plan
100%
100%
Least-privilege IAM scoping
90%
100%
No credentials in code
100%
100%
Encryption at rest
100%
100%
Encryption in transit
100%
100%
Public/private subnet separation
62%
100%
Multi-AZ / no single points of failure
100%
100%
IAM roles used (not access keys)
100%
100%
95%
17%Healthcare Patient Records Disaster Recovery Plan
Disaster recovery workflow validation checkpoints
DR testing not skipped
100%
100%
Post-DR test RTO/RPO documentation
100%
100%
Pre-cutover connectivity validation
0%
50%
Post-migration health check
100%
100%
Specific RTO/RPO targets stated
100%
100%
Named DR pattern
100%
100%
Multi-region deployment
100%
100%
No single point of failure
100%
100%
IaC for DR environment
0%
100%
Defined recovery waves
100%
100%
Monitoring in operate phase
100%
100%
Encryption maintained
33%
100%
89%
33%AWS Infrastructure Cost Reduction Initiative
AWS-specific compute and storage cost optimization techniques
EBS gp3 migration
0%
100%
Lambda ARM64/Graviton2
0%
100%
VPC gateway endpoints
0%
0%
S3 Intelligent-Tiering
87%
100%
FinOps commitment tiers
100%
100%
Right-sizing thresholds
66%
77%
Auto-Scaling target tracking at 60%
100%
100%
Cost analysis CLI usage
100%
100%
CloudFront cache optimization
37%
100%
Cost allocation tags
12%
100%
Spot for batch/fault-tolerant
100%
100%
No overly complex solutions
100%
100%
- Repository
- jeffallan/claude-skills
- Commit
5b76101
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.