cloud-architect-master

Elite Cloud and Multi-Cloud Architect Master Skill.

Quality

11%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/cloud-architect-master/SKILL.md

Quality

Discovery

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 is essentially a title masquerading as a description. It provides no actionable information about what the skill does, when to use it, or how it differs from other cloud-related skills. The use of superlatives ('Elite', 'Master') adds no value and constitutes empty fluff.

Suggestions

Replace the title-like text with specific actions the skill performs (e.g., 'Designs cloud architectures, configures multi-cloud deployments, optimizes cloud costs, migrates workloads between providers').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions AWS, Azure, GCP, cloud migration, infrastructure design, or multi-cloud strategy').

Remove superlatives like 'Elite' and 'Master' and instead describe the specific cloud platforms and architectural patterns this skill handles to create distinctiveness.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Elite Cloud and Multi-Cloud Architect Master Skill' is entirely abstract with buzzwords like 'Elite' and 'Master' but no indication of what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of capabilities.	1 / 3
Trigger Term Quality	While 'Cloud' and 'Multi-Cloud' are domain terms, they are overly generic and lack natural user keywords. No specific triggers like 'AWS', 'Azure', 'deploy', 'infrastructure', or 'migrate' are present.	1 / 3
Distinctiveness Conflict Risk	Extremely generic - 'Cloud' could conflict with any cloud-related skill. No distinguishing features or specific niche is defined to differentiate it from other potential cloud skills.	1 / 3
	Total	4 / 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 reads more like a conceptual overview or role description than actionable guidance. It lists cloud architecture topics and tool names but provides no executable code, specific commands, or concrete examples that Claude could actually use. The content assumes Claude needs to be told what cloud architecture concepts exist rather than providing specific, actionable instructions for implementation.

Suggestions

Replace conceptual bullet points with executable code examples (e.g., actual Terraform modules, AWS CLI commands, or specific configuration snippets)

Add concrete validation steps to the Execution Protocol with specific commands to verify infrastructure state

Remove the role-playing framing ('You are a Principal Cloud Architect') and focus on specific, actionable instructions

Include at least one complete, copy-paste-ready example for a common task like VPC setup or cost audit

Dimension	Reasoning	Score
Conciseness	The content is moderately efficient but includes some unnecessary framing ('You are a Principal Cloud Architect') and explanatory subheadings that Claude doesn't need. The bullet points are reasonably tight but could be more direct.	2 / 3
Actionability	The skill provides only high-level concepts and tool names without any executable code, commands, or concrete examples. Statements like 'Implement AWS Direct Connect' and 'Design for single-pane-of-glass management' are vague directions rather than actionable instructions.	1 / 3
Workflow Clarity	The 'Execution Protocol' section lists steps but they are abstract ('Audit Infrastructure', 'Design Architecture') with no concrete validation checkpoints, specific commands, or feedback loops. The reference to a checklist file doesn't provide actual workflow guidance.	1 / 3
Progressive Disclosure	The skill attempts progressive disclosure with references to sub-skills and resources, but the main content is a wall of conceptual bullet points that could be better organized. The reference to 'cost_optimization_checklist.md' is appropriate but the inline content lacks clear navigation signals.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

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