Elite Cloud and Multi-Cloud Architect Master Skill. Covers AWS/Azure/GCP, hybrid clouds, cloud-native networking, security audits, and infrastructure cost optimization. Replaces all fragmented cloud architecture skills.
41
Quality
27%
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-master/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.
This description suffers from marketing-style language ('Elite', 'Master Skill') rather than functional clarity. It lists broad domains without specifying concrete actions Claude would perform, and critically lacks any 'Use when...' guidance for skill selection. The claim to replace 'all fragmented cloud architecture skills' is vague and doesn't help Claude understand when to select this skill.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks about cloud architecture, AWS/Azure/GCP services, infrastructure design, cloud migration, or multi-cloud deployments'
Replace category labels with specific actions: instead of 'security audits' use 'perform cloud security audits, review IAM policies, analyze network configurations'
Remove marketing language ('Elite', 'Master Skill', 'Replaces all fragmented') and focus on functional capabilities that help Claude distinguish this skill from others
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cloud architecture) and lists some areas (AWS/Azure/GCP, hybrid clouds, networking, security audits, cost optimization), but these are broad categories rather than concrete actions. No specific verbs describing what the skill actually does. | 2 / 3 |
Completeness | Describes what domains it covers but lacks any explicit 'Use when...' clause or trigger guidance. The 'when' is completely missing - no indication of what user requests should activate this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant cloud platform names (AWS, Azure, GCP) and terms like 'hybrid clouds', 'security audits', 'cost optimization', but missing common user phrases like 'deploy', 'migrate', 'scale', 'cloud infrastructure', 'serverless', or specific service names users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | The claim to 'replace all fragmented cloud architecture skills' and cover multiple clouds makes it broad. While cloud-specific, terms like 'security audits' and 'cost optimization' could overlap with general security or FinOps skills. | 2 / 3 |
Total | 7 / 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 high-level overview or table of contents than actionable guidance. It names many tools and concepts (Terraform, ArgoCD, VPC Design) but provides no executable code, specific commands, or concrete implementation steps. The workflow section lacks validation checkpoints critical for cloud infrastructure operations.
Suggestions
Add executable code examples for key operations (e.g., Terraform module for VPC setup, AWS CLI commands for security audits, cost analysis scripts)
Replace abstract instructions like 'Implement AWS Direct Connect' with specific step-by-step procedures including validation commands
Add explicit validation checkpoints to the Execution Protocol (e.g., 'Run terraform plan and verify no destructive changes before apply')
Include concrete security audit commands (e.g., 'aws s3api list-buckets --query...' to find public buckets) rather than just listing what to scan for
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary framing ('You are a Principal Cloud Architect') and explanatory subheadings that Claude doesn't need. The bullet points are mostly lean but could be tighter. | 2 / 3 |
Actionability | The skill provides high-level concepts and tool names but lacks concrete, executable guidance. No actual code, commands, or specific implementation steps are provided—just abstract descriptions like 'Implement AWS Direct Connect' without showing how. | 1 / 3 |
Workflow Clarity | The 'Execution Protocol' section lists vague steps ('Audit Infrastructure', 'Design Architecture') without clear sequences, validation checkpoints, or feedback loops. For complex cloud operations involving security audits and cost optimization, this lacks the necessary rigor. | 1 / 3 |
Progressive Disclosure | The internal menu provides some structure and there's a reference to an external checklist file, but the content is mostly a monolithic overview. The referenced resource path suggests deeper content exists but navigation is minimal. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
3395991
Table of Contents
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.