cloud-architect

Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost optimization, disaster recovery, landing zones, security architecture, serverless design.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

85%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 highly actionable with well-structured, executable examples and strong validation-backed workflows. The weakest dimension is conciseness, where the generic best-practice constraint lists add tokens restating what Claude already knows.

Suggestions

Trim the 'MUST DO'/'MUST NOT DO' lists to non-obvious, skill-specific constraints (e.g., specific RTO/RPO targets, required tag schemas) and drop generic cloud hygiene Claude already knows.

Complete the truncated ALB target-group ARN and inline the trust-policy.json so the IAM example is fully copy-pasteable without external files.

Replace a few of the inline Terraform pattern blocks with a pointer to a references file if they duplicate content already covered there, to keep the body a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tables and terse code blocks, but the 'MUST DO'/'MUST NOT DO' constraints restate well-known cloud best practices Claude already knows (e.g., 'Store credentials in code', 'Skip encryption', 'Use managed services when possible').	3 / 5
Actionability	Provides copy-paste-ready executable bash and Terraform for the common cases — scoped IAM roles, public/private VPC subnets, target-tracking ASG, and cost-and-usage CLI queries — with only trivial gaps like a truncated ARN.	5 / 5
Workflow Clarity	A clear six-step sequence is paired with explicit validation checkpoints ('After Design', 'Before Migration cutover', 'After Migration', 'After DR test'), each backed by executable verification commands for the destructive/batch migration and DR operations.	5 / 5
Progressive Disclosure	A Reference Guide table signals five one-level-deep references/*.md files (all present on disk) with a 'Load When' navigation column, keeping the body an overview while detail lives in separate files.	5 / 5
	Total	18 / 20 Passed

Description

88%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, comprehensive in concrete actions, and explicit about both what it does and when to invoke it. The main gap is minor overlap risk from its broad multi-domain scope and a few missing trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the cloud domain across AWS, Azure, and GCP and lists four concrete actions — 'Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what ('Designs... creates... generates... produces...') and when ('Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger phrasing in 'Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments' plus a broad 'Invoke for...' clause; a few synonyms and file/extension variants are missing, so it sits just below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Clear multi-cloud architecture niche with distinct triggers (Well-Architected, landing zones, DR), but the very broad scope (architecture + migration + cost + security + serverless) creates minor overlap risk with the related skills named in metadata.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: jeffallan/claude-skills
Path: skills/cloud-architect/SKILL.md
Commit: 882ef55

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