multi-cloud-architecture

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

1.07x

Quality

70%

Does it follow best practices?

Impact

99%

1.07x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/multi-cloud-architecture/SKILL.md

The canonical home for this skill is multi-cloud-architecture in wshobson/agents

Quality

Content

57%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.

A well-organized conceptual reference with useful cross-cloud mappings, but it reads as a static catalog rather than actionable guidance: no executable code, no validation checkpoints in the migration workflow, and reference files are cited that are not present in the bundle.

Suggestions

Add at least one concrete, executable artifact (e.g. a minimal Terraform/OpenTofu snippet or a CLI command) so the guidance is copy-paste ready, not just descriptive.

Insert explicit validation/verification checkpoints into the Migration Strategy phases (e.g. validate IaC plan, run integration tests during dual-run) to lift workflow clarity above the destructive-operation cap of 3.

Create the referenced files references/service-comparison.md and references/multi-cloud-patterns.md (or remove the citations) and move the inlined comparison tables there to fix the broken references and reduce body tokens.

Dimension	Reasoning	Score
Conciseness	Mostly lean lists and tables that assume Claude knows the providers (no padding explaining what EC2 or S3 is), with only minor sections that could be trimmed. Not a 5 because the inline service-comparison tables duplicate content the body itself says lives in references/service-comparison.md, adding tokens that could be offloaded.	4 / 5
Actionability	Provides concrete decision guidance via named service mappings and named abstraction tools (Kubernetes, Terraform, Prometheus), but offers no executable code or commands — the Abstraction Layers diagram is ASCII pseudocode and Terraform is mentioned without any snippet. Fits the "some concrete guidance but incomplete" anchor rather than the fully-executable 5.	3 / 5
Workflow Clarity	The Migration Strategy is a clear four-phase sequence (Assessment, Pilot, Migration, Optimization) but has no validation or verification checkpoints, and migration is a destructive/batch operation, so per the cap it cannot exceed 3. Not a 2 because the sequence itself is coherent and well-bulleted.	3 / 5
Progressive Disclosure	Section structure is clear and references are signaled ("See references/service-comparison.md for complete comparison"), but the referenced files do not exist in the bundle and the comparison tables are inlined rather than offloaded, fitting the "some structure, content that should be separate is inline" anchor. Not a 4 because the broken/missing reference files undermine navigation.	3 / 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.

A strong, well-structured description that clearly states both capability and trigger conditions in third person with concrete provider names. Minor gains are possible by adding a few more action verbs and synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Design multi-cloud architectures", "select and integrate services across AWS, Azure, and GCP", "avoiding vendor lock-in", "leveraging best-of-breed services" — with only minor coverage gaps (no mention of migration or cost optimization as actions). Not a 5 because the actions stay at the design/selection level rather than enumerating a comprehensive set.	4 / 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") with concrete trigger phrases, matching the anchor exactly.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say — "multi-cloud systems", "vendor lock-in", "best-of-breed services", and the three provider names — giving good keyword coverage. Not a 5 because common synonyms like "migrate between clouds" or "cloud portability" are absent.	4 / 5
Distinctiveness Conflict Risk	Has a clear multi-cloud niche with provider-specific triggers, but overlaps with closely related skills it itself names (terraform-module-library, cost-optimization, hybrid-cloud-networking), so minor conflict risk remains. Not a 5 because of that stated overlap.	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
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/multi-cloud-architecture/SKILL.md
Commit: 6453c0b

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