multi-cloud-architecture

Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, GCP, and OCI. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.

Quality

68%

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 ./plugins/cloud-infrastructure/skills/multi-cloud-architecture/SKILL.md

Quality

Content

53%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 well-organized with real one-level-deep references and useful service-mapping tables, but it over-explains basics Claude knows, lacks executable code, and the migration workflow omits the validation checkpoints required for destructive multi-cloud operations.

Suggestions

Add explicit validation/failover-verification checkpoints between Migration Strategy phases (e.g., verify cutover success and rollback readiness before proceeding) so the destructive multi-cloud workflow can score higher.

Trim well-known best practices (e.g., 'Use managed services when possible', 'Right-size resources') and consider moving the full compute/storage/database tables into the existing service-comparison reference to reduce duplication.

Replace the ASCII abstraction-layer diagram with an executable example (e.g., a minimal Terraform/OpenTofu snippet) or concrete commands to make the guidance copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient tables and lists, but it re-explains widely known cloud service mappings and basic best practices (e.g., 'Use managed services when possible', 'Right-size resources') that Claude already knows, so it could be tightened.	3 / 5
Actionability	It provides concrete service mappings and named tools (Terraform/OpenTofu, Kubernetes, Prometheus/Grafana), but the abstraction-layer diagram is pseudocode and there is no executable code or concrete commands a user can run.	3 / 5
Workflow Clarity	The Migration Strategy lists four sequenced phases, but a multi-cloud migration is a high-risk batch/destructive operation with no validation checkpoints or failover-verification steps, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Structure is good: the SKILL.md is an overview with two well-signaled one-level-deep references ('See references/service-comparison.md', 'See references/multi-cloud-patterns.md') that are real files, though the inlined service tables duplicate the comparison reference.	4 / 5
	Total	13 / 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 and complete: it states concrete capabilities across four named providers and supplies explicit 'Use when' triggers covering the main multi-cloud scenarios. Specificity is the only soft spot, with just two named actions.

Dimension	Reasoning	Score
Specificity	Names the multi-cloud domain plus two concrete actions ('select and integrate services across AWS, Azure, GCP, and OCI'), but only two actions are stated rather than several, fitting just above anchor 3.	3.5 / 5
Completeness	Explicitly answers both what ('Design multi-cloud architectures using a decision framework to select and integrate services') and when ('Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services').	5 / 5
Trigger Term Quality	Natural user phrases like 'building multi-cloud systems', 'avoiding vendor lock-in', and 'leveraging best-of-breed services' provide good trigger coverage, though a few synonyms or common variations are missing.	4 / 5
Distinctiveness Conflict Risk	The explicit four-provider scope (AWS, Azure, GCP, OCI) carves a clear multi-cloud niche with minimal conflict risk, though 'best-of-breed services' has minor overlap with general cloud-architecture skills.	4.5 / 5
	Total	17 / 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: wshobson/agents
Path: plugins/cloud-infrastructure/skills/multi-cloud-architecture/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours 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.