multi-cloud-architecture
tessl i github:wshobson/agents --skill multi-cloud-architectureDesign 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.
Review Score
64%
Validation Score
13/16
Implementation Score
35%
Activation Score
90%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs |
Implementation
Suggestions 4
Score
35%Overall Assessment
This skill provides a useful reference framework for multi-cloud architecture decisions with good comparison tables, but lacks the actionable, executable guidance that would make it truly useful. It reads more like a conceptual overview than a skill that enables Claude to actually implement multi-cloud architectures. The content describes what to do without showing how to do it.
Suggestions
- Add executable Terraform code examples showing how to implement at least one multi-cloud pattern (e.g., the cloud-agnostic abstraction pattern with actual module code)
- Include specific CLI commands for common multi-cloud operations (e.g., setting up cross-cloud networking, configuring replication)
- Add validation checkpoints to the migration strategy with specific commands to verify each phase (e.g., 'Run `terraform plan` to verify no drift', 'Test failover with `kubectl drain`')
- Remove or condense the generic 'Best Practices' section - these are standard DevOps practices Claude already knows
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The content is reasonably efficient with good use of tables, but includes some unnecessary framing ('Purpose', 'When to Use' sections) and generic best practices that Claude already knows. The comparison tables are valuable, but some sections like 'Best Practices' list obvious guidance. |
Actionability | 1/3 | The skill is almost entirely descriptive with no executable code, commands, or concrete implementation examples. Patterns are described abstractly ('Database replication across clouds') without showing how to actually implement them. The abstraction layer diagram is conceptual, not actionable. |
Workflow Clarity | 2/3 | The migration strategy has clear phases, but lacks validation checkpoints and specific verification steps. There's no guidance on how to verify each phase succeeded before proceeding, and no feedback loops for error recovery during migration. |
Progressive Disclosure | 2/3 | References to external files are present and clearly signaled, but the main document contains substantial content that could be better organized. The service comparison tables could be in the referenced file, with just key decision criteria in the main skill. |
Activation
Suggestions 1
Score
90%Overall Assessment
This is a well-structured description with excellent trigger terms and completeness. The explicit 'Use when...' clause with multiple trigger scenarios is a strength. The main weakness is that the capabilities could be more specific about what concrete actions the skill enables beyond the general 'design' and 'select and integrate'.
Suggestions
- Add 2-3 more specific concrete actions such as 'evaluate service equivalents across providers', 'design cross-cloud networking', or 'plan data residency strategies' to improve specificity.
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (multi-cloud architectures) and mentions 'decision framework' and 'select and integrate services', but doesn't list specific concrete actions like 'design network topology', 'configure cross-cloud IAM', or 'set up data replication'. |
Completeness | 3/3 | Clearly 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 explicit trigger guidance. |
Trigger Term Quality | 3/3 | Includes strong natural keywords users would say: 'multi-cloud', 'AWS', 'Azure', 'GCP', 'vendor lock-in', 'best-of-breed'. These are terms users naturally use when discussing multi-cloud architecture decisions. |
Distinctiveness Conflict Risk | 3/3 | The multi-cloud focus with all three major providers (AWS, Azure, GCP) and specific triggers like 'vendor lock-in' and 'best-of-breed' create a clear niche that's unlikely to conflict with single-cloud or general architecture skills. |
- Repository
- github.com/wshobson/agents
- Last updated
- Created
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.