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.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid cloud architecture skill with strong actionability through executable CLI and Terraform examples, and a well-structured workflow with explicit validation checkpoints. Its main weakness is that it tries to serve as both an overview and a detailed reference—the inline code patterns are extensive for a top-level file that already has a reference table pointing to detailed guides. The missing bundle files make it impossible to verify the progressive disclosure structure works in practice.

Suggestions

Move the detailed Terraform patterns (VPC, ASG, IAM) into the referenced files (e.g., references/aws.md) and keep only one brief example inline to demonstrate the style.

Consolidate the MUST DO/MUST NOT DO lists to eliminate conceptual overlap (e.g., merge 'implement security by design' and 'skip encryption' into a single directive).

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 providing both AWS CLI and Terraform for the IAM example adds bulk. Some patterns like the VPC and ASG Terraform blocks are lengthy for a top-level skill file that should be an overview pointing to references.	2 / 3
Actionability	The skill provides fully executable CLI commands and complete Terraform configurations across multiple cloud providers. The validation checkpoints include copy-paste ready commands for checking VPC peering, target group health, and cost analysis.	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). Each checkpoint includes concrete verification commands and clear pass/fail criteria, with the migration cutover checkpoint being a proper gate ('validate before proceeding').	3 / 3
Progressive Disclosure	The reference table with 'Load When' guidance is well-structured and signals one-level-deep references clearly. However, no bundle files were provided, so the referenced files (references/aws.md, references/azure.md, etc.) cannot be verified. Additionally, substantial inline code examples (VPC, ASG, IAM patterns) could be moved to reference files, keeping the SKILL.md leaner as an overview.	2 / 3
	Total	10 / 12 Passed

Description

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

Validation

100%

Warnings & errors only

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: e8be415

Reviewed: 21 days ago

Table of Contents

Discovery Implementation Validation

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.