cloud-architect
Expert 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.
55
Quality
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/cloud-architect/SKILL.mdQuality
Discovery
82%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 description has strong trigger term coverage and completeness with an explicit 'Use PROACTIVELY for...' clause. However, it relies heavily on role-based language ('Expert cloud architect', 'Masters') rather than concrete action verbs describing what the skill does. The description would benefit from replacing identity claims with specific capabilities.
Suggestions
Replace role-based language ('Expert cloud architect specializing', 'Masters') with action verbs describing concrete capabilities (e.g., 'Designs multi-cloud infrastructure, writes Terraform/CDK modules, analyzes cloud costs')
Add more specific file types or artifacts the skill produces (e.g., 'generates architecture diagrams, Terraform configurations, cost analysis reports')
| 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 architecture, IaC, FinOps, architectural patterns) and when ('Use PROACTIVELY for cloud architecture, cost optimization, migration planning, or multi-cloud strategies') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'AWS', 'Azure', 'GCP', 'Terraform', 'CDK', 'serverless', 'microservices', 'cost optimization', 'migration', 'multi-cloud' are all terms users naturally use when seeking cloud architecture help. | 3 / 3 |
Distinctiveness Conflict Risk | While cloud-specific, terms like 'infrastructure design', 'security', 'compliance' could overlap with general DevOps or security-focused skills. The multi-cloud and IaC focus provides some distinction but 'architectural patterns' is broad. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content functions as a hollow index rather than actionable guidance. It lists nine sub-skill categories and references external files but provides no concrete instructions, code examples, or specific workflows that Claude could immediately apply. The generic instructions ('Clarify goals', 'Apply best practices') add no value beyond what Claude already knows.
Suggestions
Add at least one concrete, executable example for a common task (e.g., a Terraform snippet for a basic multi-AZ setup or a cost optimization checklist with specific AWS/Azure commands)
Replace the generic four-step instructions with specific workflows for 2-3 common scenarios (e.g., 'For new infrastructure: 1. Run cost estimate with `infracost breakdown` 2. Validate with...')
Include a quick-reference section with specific commands, CLI tools, or decision trees that provide immediate value without requiring navigation to sub-skills
Remove or condense the 'Use this skill when' boilerplate and Purpose section—these explain concepts Claude already understands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary filler like the generic 'Use this skill when' section and vague purpose statement that Claude doesn't need. The capabilities section is just a list of links without substance. | 2 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. Instructions are entirely abstract ('Clarify goals', 'Apply relevant best practices') with no specific examples, patterns, or copy-paste ready content for any cloud architecture task. | 1 / 3 |
Workflow Clarity | The four-step instructions are vague platitudes without any sequencing for actual cloud architecture tasks. No validation checkpoints, no specific workflows for common operations like infrastructure deployment or cost analysis. | 1 / 3 |
Progressive Disclosure | References to sub-skills and implementation-playbook.md show some structure, but the main file provides almost no useful overview content—it's essentially just a table of contents with no quick-start guidance or actionable summary. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.