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.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/cloud-architect/SKILL.md

Quality

Content

23%Weight 40%Scale 1-5

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

The body is a verbose capability catalogue that restates cloud knowledge Claude already has, with vague non-executable instructions and a broken reference to a missing playbook file. It needs aggressive trimming, concrete examples or IaC snippets, and real validation feedback loops.

Suggestions

Remove the Capabilities service catalogues, Behavioral Traits, and Knowledge Base sections — they restate well-known cloud knowledge; replace with only the non-obvious guidance, decision rules, or templates Claude would not already produce.

Add concrete, executable artifacts: a minimal Terraform/CDK module skeleton or a worked migration/FinOps example with copy-paste commands, instead of abstract steps like "Recommend appropriate cloud services".

Either create `resources/implementation-playbook.md` with the detailed playbooks the body points to, or remove the dangling reference; add explicit validate -> fix -> re-run checkpoints for destructive IaC/infrastructure changes.

Dimension	Reasoning	Score
Conciseness	The body is heavily padded with enumerations of cloud services Claude already knows (full AWS/Azure/GCP service catalogs in Capabilities, plus a Knowledge Base and Behavioral Traits restating obvious best practices), offering little that Claude does not already know.	1 / 5
Actionability	Guidance is high-level and abstract ("Apply relevant best practices and validate outcomes", "Recommend appropriate cloud services") with no executable code, commands, or concrete IaC examples; the only detail pointer is to a non-existent file.	2 / 5
Workflow Clarity	A rough sequence exists (Instructions bullets and the 8-step Response Approach) and validation is mentioned generically ("validate outcomes", "verification"), but there are no explicit validation checkpoints or fix-retry feedback loops for destructive infrastructure/batch operations, capping this at 3.	3 / 5
Progressive Disclosure	Most detail (large service catalogs, architecture patterns) is inlined in SKILL.md rather than split into reference files, and the single outbound reference to `resources/implementation-playbook.md` points to a file that does not exist, breaking navigation.	2 / 5
	Total	8 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 is strong: third-person voice, explicit what-and-when structure, and a concrete PROACTIVELY trigger phrase with good natural keyword coverage. It is held back only by breadth-related distinctiveness overlap and domain-level rather than action-level specificity.

Dimension	Reasoning	Score
Specificity	Lists several specific capability areas ("infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization") plus concrete activities like migration planning, but stays at the domain-area level rather than enumerating discrete concrete actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly states both what ("Expert cloud architect specializing in ... infrastructure design, advanced IaC, FinOps cost optimization") and when ("Use PROACTIVELY for cloud architecture, cost optimization, migration planning, or multi-cloud strategies") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage with "cloud architecture, cost optimization, migration planning, multi-cloud strategies" and provider/tool names (AWS/Azure/GCP, Terraform/OpenTofu/CDK), though a few common variations a user might say are not present.	4 / 5
Distinctiveness Conflict Risk	"Cloud architect" is a recognizable niche with distinct multi-cloud/IaC/FinOps triggers, but the breadth of the cloud domain carries minor overlap risk with adjacent cloud-ops or devops skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: duclm1x1/Dive-Ai
Path: docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/cloud-architect/SKILL.md
Commit: 20ba150

Reviewed: 5 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.