cloud-architect
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.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill cloud-architectOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 has strong trigger term coverage and clear distinctiveness for cloud architecture work, but suffers from a lack of concrete action descriptions. It tells Claude when to use the skill but not what the skill actually does - it reads more like a topic list than a capability description.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Designs cloud architectures, creates migration plans, generates cost optimization recommendations, produces disaster recovery strategies.'
Restructure to lead with capabilities before the 'Use when' clause, following the pattern: '[What it does]. Use when [triggers].'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cloud architectures) and lists several areas like 'Well-Architected Framework, cost optimization, disaster recovery' but these are topics/concepts rather than concrete actions. Missing action verbs describing what the skill actually does (e.g., 'designs', 'analyzes', 'generates'). | 2 / 3 |
Completeness | Has a clear 'Use when...' clause which is good, but the 'what does this do' portion is weak - it lists topics to invoke for but doesn't explain what actions or outputs the skill provides. The description tells when to use it but not what it actually does. | 2 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'cloud architectures', 'migrations', 'multi-cloud', 'cost optimization', 'disaster recovery', 'landing zones', 'security architecture', 'serverless'. These are terms practitioners commonly use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche in cloud architecture with specific triggers like 'Well-Architected Framework', 'landing zones', 'multi-cloud deployments' that are unlikely to conflict with other skills. The combination of terms creates a distinct cloud infrastructure focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level framework for cloud architecture work with good progressive disclosure to reference files. However, it severely lacks actionability - there are no executable code examples, CLI commands, or concrete configurations. The content reads more like a job description than an actionable skill that would help Claude perform specific tasks.
Suggestions
Add concrete, executable examples for key tasks - e.g., a Terraform snippet for a basic VPC setup, AWS CLI commands for cost analysis, or a CloudFormation template fragment
Include specific validation steps in the workflow - e.g., 'Run `terraform plan` and verify no unexpected changes before applying' or 'Validate DR with `aws rds describe-db-cluster-snapshots`'
Remove or condense the 'Knowledge Reference' section as it adds no actionable value - Claude already knows these technologies exist
Add concrete output examples showing what a good architecture diagram description or cost estimation should look like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity like the role definition explaining '15+ years of experience' and listing concepts Claude already knows. The 'Knowledge Reference' section is largely redundant as it just lists technologies without adding actionable value. | 2 / 3 |
Actionability | The skill is almost entirely abstract guidance with no concrete code, commands, or executable examples. Phrases like 'Implement zero-trust' and 'Use infrastructure as code' describe rather than instruct. No Terraform snippets, CLI commands, or specific configuration examples are provided. | 1 / 3 |
Workflow Clarity | The 6-step core workflow provides a reasonable sequence, but lacks validation checkpoints and feedback loops. For complex operations like migrations and disaster recovery, there are no explicit verification steps or error recovery guidance. | 2 / 3 |
Progressive Disclosure | The skill effectively uses a reference table pointing to separate files for AWS, Azure, GCP, multi-cloud, and cost optimization topics. References are one level deep and clearly signaled with a 'Load When' column explaining context. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- Reviewed
Table of Contents
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.