Cloud Architect
ListedThis AI acts as a Cloud Architect, assisting you in designing and planning your cloud infrastructure for optimal efficiency and cost-effectiveness.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add sickn33/agentic-awesome-skills --skill cloud-architect -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
sickn33
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
Declares what it does: failed
No SKILL.md was found in the skill's directory.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned sickn33/agentic-awesome-skills at c808e6e480.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- c808e6e480
- Manifest
- skills/cloud-architect/SKILL.md
- Scanned
- 0 files
- Copies in repo
- 3 — all of them scanned
About this skill
What it does
This skill allows an AI agent to act as a Cloud Architect, providing guidance and expertise in designing and planning cloud infrastructure. It leverages deep knowledge of major cloud platforms (AWS, Azure, Google Cloud) and modern architectural patterns like serverless and microservices. The goal is to help users create scalable, cost-effective, and secure multi-cloud solutions while adhering to best practices.
When to use it
- You're working on tasks related to designing or planning cloud infrastructure.
- You need guidance on best practices for cloud architecture.
- You require a checklist or framework for implementing cloud solutions.
- You are exploring multi-cloud strategies, including disaster recovery and vendor lock-in mitigation.
Key capabilities
- Expertise in AWS (EC2, Lambda, EKS, RDS, S3, VPC, IAM, CloudFormation, CDK, Well-Architected Framework)
- Expertise in Azure (Virtual Machines, Functions, AKS, SQL Database, Blob Storage, Virtual Network, ARM templates, Bicep)
- Expertise in Google Cloud (Compute Engine, Cloud Functions, GKE, Cloud SQL, Cloud Storage, VPC, Cloud Deployment Manager)
- Proficiency in Infrastructure as Code tools like Terraform/OpenTofu, CloudFormation, ARM/Bicep, and AWS CDK.
- Knowledge of GitOps practices using tools like ArgoCD, Flux, and GitHub Actions.
Example prompts
- "I need to design a serverless application on AWS. Can you provide a checklist for security best practices?"
- "What are the key considerations when implementing a multi-cloud disaster recovery strategy?"
- "Can you give me an example of how to use Terraform modules effectively in AWS?"
Tips & gotchas
- Clearly define your goals, constraints, and required inputs before engaging with the skill.
- The skill's expertise is limited to cloud architecture; it cannot handle unrelated tasks or integrations outside this scope.
- For detailed implementation examples, refer to the
resources/implementation-playbook.mdfile.