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.
95
92%
Does it follow best practices?
Impact
96%
1.14xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities across multiple cloud platforms, provides explicit trigger guidance with both 'Use when' and 'Invoke for' clauses, and includes a rich set of natural keywords users would employ. It uses proper third-person voice throughout and is well-structured for skill selection among many options.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'designs cloud architectures', 'creates migration plans', 'generates cost optimization recommendations', 'produces disaster recovery strategies', and names specific platforms (AWS, Azure, GCP). | 3 / 3 |
Completeness | Clearly answers both 'what' (designs architectures, creates migration plans, generates cost recommendations, produces DR strategies) and 'when' with explicit 'Use when...' and 'Invoke for...' clauses listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'cloud architectures', 'migration plans', 'cost optimization', 'disaster recovery', 'AWS', 'Azure', 'GCP', 'Well-Architected Framework', 'landing zones', 'security architecture', 'serverless design', 'multi-cloud'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in multi-cloud architecture across AWS/Azure/GCP. The specific mentions of Well-Architected Framework, landing zones, and serverless design create a distinct identity unlikely to conflict with generic infrastructure or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured cloud architecture skill with strong actionability through executable CLI and Terraform examples, clear workflow sequencing with validation checkpoints, and good progressive disclosure via a reference table. The main weakness is moderate verbosity—some patterns could be trimmed (e.g., showing both CLI and Terraform for the same concept) and the MUST/MUST NOT lists contain some obvious guidance that Claude already knows.
Suggestions
Trim the MUST DO/MUST NOT DO lists to only non-obvious, project-specific constraints rather than general best practices Claude already knows (e.g., 'don't store credentials in code').
Consider showing only one implementation approach per pattern (CLI or Terraform, not both) to reduce token usage, or move the dual examples into a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy—the MUST DO/MUST NOT DO lists overlap conceptually (e.g., 'implement security by design' vs 'skip encryption'), and showing both AWS CLI and Terraform for the same IAM pattern is arguably excessive. Some sections like Output Templates are thin enough to question their value. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands and complete Terraform configurations across multiple patterns (IAM, VPC, ASG, cost analysis). The validation checkpoints include real, copy-paste-ready commands for AWS and Azure. | 3 / 3 |
Workflow Clarity | The 6-step core workflow is clearly sequenced with explicit validation checkpoints at critical stages (after design, before migration cutover, after migration, after DR test). The migration cutover checkpoint includes a validate-then-proceed gate, which is appropriate for this destructive/risky operation. | 3 / 3 |
Progressive Disclosure | The reference guide table clearly signals when to load each detailed reference file (aws.md, azure.md, gcp.md, multi-cloud.md, cost.md) with specific trigger conditions. The main skill stays at overview level with inline examples for common patterns while deferring deep provider-specific guidance to one-level-deep references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- Reviewed
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.