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.
28
20%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/cloud-architect/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description reads more like a resume headline than a skill selection guide. While it names relevant technologies and domains, it lacks concrete actions Claude would perform and entirely omits trigger guidance ('Use when...'). The first-person framing implied by 'Expert cloud architect specializing in' also deviates from the preferred third-person voice.
Suggestions
Add an explicit 'Use when...' clause listing trigger scenarios, e.g., 'Use when the user asks about cloud infrastructure design, Terraform modules, cloud cost optimization, multi-cloud deployments, or IaC templates.'
Replace the resume-style opening with concrete actions in third person, e.g., 'Designs multi-cloud infrastructure across AWS/Azure/GCP, generates Terraform/OpenTofu/CDK configurations, analyzes cloud spending for cost optimization, and recommends architectural patterns.'
Include natural user-facing trigger terms and variations like 'cloud costs', 'infrastructure as code', '.tf files', 'cloud migration', 'serverless', 'VPC', 'Kubernetes cluster setup' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domains (AWS/Azure/GCP, Terraform/OpenTofu/CDK, FinOps) and some general actions (infrastructure design, cost optimization), but doesn't list specific concrete actions like 'generate Terraform modules', 'create cost reports', or 'design VPC architectures'. The terms are more category labels than actionable capabilities. | 2 / 3 |
Completeness | Describes what the skill covers at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also somewhat vague (no concrete actions), this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like AWS, Azure, GCP, Terraform, OpenTofu, CDK, FinOps, and multi-cloud that users might naturally mention. However, it misses common variations and natural phrases users would say like 'cloud costs', 'infrastructure as code', 'deploy to cloud', 'cloud migration', 'serverless', or file extensions like '.tf'. | 2 / 3 |
Distinctiveness Conflict Risk | The multi-cloud and IaC focus provides some distinctiveness, but terms like 'cloud architect' and 'modern architectural patterns' are broad enough to overlap with general DevOps, infrastructure, or architecture skills. The combination of specific tool names (Terraform, CDK) helps somewhat but 'architectural patterns' is very generic. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a job description or persona prompt rather than actionable technical guidance. It exhaustively lists cloud technologies and concepts Claude already knows without providing any concrete code, commands, templates, or specific procedures. The content would need a fundamental restructuring to become useful—replacing capability lists with executable examples, specific workflows, and concrete decision frameworks.
Suggestions
Replace the extensive capability lists with concrete, executable examples: Terraform module templates, specific CLI commands for cost analysis, architecture decision records with actual code snippets.
Add specific multi-step workflows with validation checkpoints, e.g., a Terraform deployment workflow with plan review, apply, and post-deployment verification steps including rollback procedures.
Remove sections that describe what Claude already knows (cloud service catalogs, behavioral traits, knowledge base) and replace with project-specific conventions, naming standards, tagging schemas, or organizational policies that Claude wouldn't know.
Create actual bundle files (e.g., terraform-patterns.md, cost-optimization-checklist.md, security-baseline.md) with concrete reference material and update the SKILL.md to be a concise overview pointing to these resources.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose. The vast majority of content is listing capabilities, services, and concepts Claude already knows (AWS services, architectural patterns, security frameworks, etc.). The 'Capabilities' section is essentially a resume/catalog that adds no actionable value. Behavioral traits, knowledge base, and example interactions are all padding. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance anywhere. The entire skill is abstract descriptions and lists of technologies. Instructions like 'Apply relevant best practices and validate outcomes' are vague. No Terraform examples, no CLI commands, no architecture diagram templates, no specific procedures. | 1 / 3 |
Workflow Clarity | The 'Response Approach' section lists 8 high-level steps but they are generic and lack any validation checkpoints, feedback loops, or concrete sequencing. For a skill involving infrastructure changes (potentially destructive), there are no verification steps, no rollback procedures, and no explicit validation gates. | 1 / 3 |
Progressive Disclosure | There is a reference to 'resources/implementation-playbook.md' for detailed examples, which shows some attempt at progressive disclosure. However, no bundle files exist to support this reference, and the main file itself is a monolithic wall of lists that should have been split into separate reference files for different domains (IaC, FinOps, security, etc.). | 2 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
79d9c42
- 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.