Back to catalog
Human reviewedDesign

Skill dossier

cloud-architect

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

designreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Designs AWS, Azure and GCP architectures, migration plans, cost models and disaster recovery, with validation checkpoints at design, cutover and post-migration.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Assesses current state, requirements, constraints and compliance needs.
  • Designs topology and checks that every component has a redundancy strategy.
  • Applies the 6Rs framework and validates VPC or VNet peering before migration cutover.
  • Produces cost estimates, security architecture and a deployment and rollback plan.

Limitations & scope

  • Example commands target AWS and Azure CLIs; cost examples use GNU date syntax that may differ on macOS.
  • Cost and availability targets are rules to design toward, not measured results.
  • Provider-specific detail is in separate reference files for AWS, Azure, GCP and multi-cloud.

Relevant for

  • Cloud and infrastructure architects
  • Teams planning migrations to the cloud
  • Engineers working on cost optimization or DR

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
74.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/cloud-architect/references/aws.mdReference11 KB
skills/cloud-architect/references/azure.mdReference14.1 KB
skills/cloud-architect/references/cost.mdReference14 KB
skills/cloud-architect/references/gcp.mdReference16.8 KB
skills/cloud-architect/references/multi-cloud.mdReference11.1 KB
skills/cloud-architect/SKILL.mdInstruction7.4 KB

SKILL.md frontmatter

{
  "name": "cloud-architect",
  "description": "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.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "infrastructure",
    "triggers": "AWS, Azure, GCP, Google Cloud, cloud migration, cloud architecture, multi-cloud, cloud cost, Well-Architected, landing zone, cloud security, disaster recovery, cloud native, serverless architecture",
    "role": "architect",
    "scope": "infrastructure",
    "output-format": "architecture",
    "related-skills": "devops-engineer, kubernetes-specialist, terraform-engineer, security-reviewer, microservices-architect, monitoring-expert"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Discover

    Assess current state, requirements, constraints and compliance needs.

  2. 02
    Action

    Design and secure

    Select services, design topology and data architecture, and plan the security approach.

  3. 03
    Decision

    Validate before cutover

    Confirm VPC peering or connectivity is established before migrating.

  4. 04
    Output

    Deliver architecture package

    Provide the diagram, service rationale, security architecture, cost estimate and rollback plan.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

39 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

32 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 32 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

7 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review all IAM policies and Terraform or CLI commands before applying them, and never put credentials in code.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/cloud-architect # .claude/skills/cloud-architect
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/cloud-architect/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm cloud-architect/SKILL.md exists at the destination, then ask Claude Code to use the cloud-architect skill on a small test task.

Prerequisites

  • Example commands target AWS and Azure CLIs; cost examples use GNU date syntax that may differ on macOS.
  • Cost and availability targets are rules to design toward, not measured results.
  • Provider-specific detail is in separate reference files for AWS, Azure, GCP and multi-cloud.

Example prompts

Representative task

Use the cloud-architect skill to design a two-AZ AWS architecture for a web app with private and public subnets, least-privilege IAM, auto-scaling and a disaster recovery plan with stated RTO and RPO.

Inspect before use

Read the cloud-architect skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/cloud-architect/SKILL.md and its referenced files. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Includes explicit validation checkpoints with real CLI checks before cutover.
  • Covers least-privilege IAM and cost allocation tags in examples.

Considerations

  • Pushes multi-region and 99.9%+ availability, which raises cost and complexity.
  • Examples touch IAM and networking, so mistakes can have security impact.
Research conclusion

A thorough cloud design checklist that needs careful human review before any generated IaC is applied.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/cloud-architect
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.