cloud-architect
tessl i github:sickn33/antigravity-awesome-skills --skill cloud-architectExpert cloud architect specializing in AWS/Azure/GCP multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, security, compliance, and disaster recovery. Use PROACTIVELY for cloud architecture, cost optimization, migration planning, or multi-cloud strategies.
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
Implementation
7%This skill reads like a job description or persona definition rather than actionable guidance. It extensively catalogs cloud technologies and concepts Claude already knows, while providing zero executable code, specific commands, or concrete workflows. The content would be more effective as a brief overview pointing to specific playbooks for common tasks like cost optimization, migration planning, or IaC implementation.
Suggestions
Replace capability lists with concrete, executable examples (e.g., a Terraform module template, a cost optimization checklist with specific commands)
Add specific workflows with validation steps for common tasks like 'Design a multi-region architecture' or 'Optimize cloud costs'
Move the technology catalogs to a reference file and keep SKILL.md focused on when/how to apply the skill with actionable guidance
Include at least one complete, copy-paste-ready code example (e.g., a Terraform module structure or a cost analysis script)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of technologies Claude already knows. The 'Capabilities' section is essentially a catalog of cloud services and tools that adds no actionable value - Claude doesn't need to be told what AWS EC2 or Terraform are. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. The entire skill describes capabilities and lists technologies but never shows how to actually do anything. 'Response Approach' is vague guidance, not actionable steps. | 1 / 3 |
Workflow Clarity | The 'Response Approach' section lists 8 abstract steps without any validation checkpoints, concrete sequences, or feedback loops. For complex cloud architecture tasks involving infrastructure changes, there's no guidance on verification or error recovery. | 1 / 3 |
Progressive Disclosure | References 'resources/implementation-playbook.md' for detailed examples, which is appropriate progressive disclosure. However, the main content is a monolithic wall of capability lists that should be restructured or moved to reference files. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
82%This description has strong trigger term coverage and explicit 'Use when' guidance, making it functional for skill selection. However, it relies on role-based language ('Expert cloud architect', 'Masters') rather than action-based descriptions, and its broad scope covering multiple domains (security, compliance, DR, microservices) increases potential overlap with other skills.
Suggestions
Replace role-based language ('Expert cloud architect', 'Masters') with action verbs describing what the skill does (e.g., 'Designs multi-cloud infrastructure, writes Terraform/CDK code, analyzes cloud costs')
Narrow the scope or clarify boundaries to reduce conflict risk with potential security, DevOps, or compliance-focused skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domains (AWS/Azure/GCP, Terraform/OpenTofu/CDK) and mentions actions like 'cost optimization', 'migration planning', but uses vague terms like 'Masters' and 'specializing' rather than listing concrete actions the skill performs. | 2 / 3 |
Completeness | Clearly answers both what (cloud infrastructure design, IaC, FinOps, architectural patterns) and when ('Use PROACTIVELY for cloud architecture, cost optimization, migration planning, or multi-cloud strategies'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'cloud architecture', 'AWS', 'Azure', 'GCP', 'Terraform', 'CDK', 'cost optimization', 'migration', 'multi-cloud', 'serverless', 'microservices'. These are terms users naturally use when seeking cloud help. | 3 / 3 |
Distinctiveness Conflict Risk | While cloud-specific, the broad scope covering serverless, microservices, security, compliance, and disaster recovery could overlap with dedicated security skills, DevOps skills, or general infrastructure skills. The multi-domain coverage increases conflict risk. | 2 / 3 |
Total | 10 / 12 Passed |
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.