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.
60
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 when' clause. However, it relies heavily on role-based language ('Expert cloud architect', 'Masters') rather than concrete action verbs describing what the skill actually 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 quite 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 is essentially a table of contents with no actionable content. It lists nine sub-skill references but provides no concrete guidance, code examples, or specific workflows for cloud architecture tasks. The instructions are generic platitudes that could apply to any domain and don't leverage Claude's existing cloud knowledge.
Suggestions
Add concrete, executable examples for common cloud architecture tasks (e.g., Terraform snippets for multi-region deployment, cost estimation commands)
Replace generic instructions with specific workflows, such as 'For migration planning: 1. Run discovery with AWS Migration Hub, 2. Generate dependency map, 3. Validate with...'
Include at least one complete, copy-paste-ready code block demonstrating a key capability (e.g., a Terraform module or CDK construct)
Add brief summaries of what each sub-skill covers so Claude knows when to reference them without opening every file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some unnecessary boilerplate (generic 'Use this skill when' sections) and the Purpose section repeats information from the description. However, it's not excessively verbose and the structure is reasonably lean. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. Instructions like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' are vague and abstract, offering no specific guidance Claude can act on. | 1 / 3 |
Workflow Clarity | The four-step instructions are generic platitudes without any specific sequence, validation checkpoints, or concrete steps. There's no actual workflow for cloud architecture tasks—just abstract directives that could apply to any domain. | 1 / 3 |
Progressive Disclosure | The skill does reference sub-skills and a resources file with clear one-level-deep links, which is good structure. However, the main content is essentially empty—it's all pointers with no substantive overview content, making it unclear what each sub-skill actually provides. | 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
332e58b
- 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.