Skip to content
Agentmart
Submit a tool

cloud-architect

Diseña infraestructura cloud como código — Terraform, AWS, GCP, Azure.

Skill by Leandro Benjamin L.

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/leandrobenjaminl-cloud-architect

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Diseña infraestructura cloud como código — Terraform, AWS, GCP, Azure. Arquitecturas serverless, VPC, bases de datos administradas y cost optimization. Trigger: Cuando hay que levantar infraestructura en cloud, elegir proveedor, diseñar arquitectura o escribir Terraform.

Use cases: devops, cloud

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/cloud-architect

What's inside

Skill name
cloud-architect
Description
Diseña infraestructura cloud como código — Terraform, AWS, GCP, Azure. Arquitecturas serverless, VPC, bases de datos administradas y cost optimization. Trigger: Cuando hay que levantar infraestructura en cloud, elegir proveedor, diseñar arquitectura o escribir Terraform.
License
MIT
Metadata
author: Leandro Benjamin L. · version: 1.0
Instructions
60 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Skill: cloud-architect

Infraestructura como código en serio. Nada de consolear.

## Trigger

- Necesitás levantar una base de datos, un bucket o un servidor
- Hay que elegir entre AWS, GCP o Azure
- Vas a deployar una app web y necesitás DNS + CDN + SSL
- Querés infraestructura reproducible (Terraform)
- Hay que auditar costos y recursos olvidados

## Workflow LEND

```
1. ANALIZAR
   ├── Tipo de carga: web app, batch processing, API serverless
   ├── Escala esperada: users/día, storage, bandwidth
   ├── Presupuesto: free tier, startup, enterprise
   ├── ¿Ya hay cuenta en algún proveedor?
   └── Requisitos de compliance (GDPR, datos locales)

2. OFRECER (Menú del Senior)
   ├── A) Serverless: Lambda/Cloud Functions + API Gateway + DynamoDB/Firestore
   ├── B) Containerizado: ECS/GKE/AKS + RDS/Cloud SQL + ALB
   └── C) VM clásica: EC2/GCE/VM + managed DB + Load Balancer

3. ELEGIR → el usuario confirma

4. HACER
   ├── Terraform HCL (o OpenTofu): main.tf, variables.tf, outputs.tf
   ├── Remote state en S3/GCS + DynamoDB/Bigtable locking
   ├── Resource tagging consistente (Project, Env, ManagedBy)
   ├── Security groups / firewall rules (mínimo privilegio)
   └── Cost estimation con infracost o similar

5. VERIFICAR
   ├── terraform plan pasa sin errores
   ├── Los recursos son los mínimos necesarios
   └── No hay secretos en los outputs
```

## Patrones

- **Estado remoto**: siempre S3/GCS + locking, nunca local
- **Tagging**: `Project`, `Environment`, `ManagedBy`, `CostCenter`
- **Naming**: `{project}-{env}-{resource}-{region}-{xxx}`
- **Mínimo privilegio**: IAM roles, security groups, service accounts
- **Cost tags**: marcar recursos para trackear gasto
- **Módulos**: reutilizar módulos de Terraform Registry

## Anti-patrones

- Terraform state en local (se pierde, no se comparte)
- Recursos sin tags (no se puede rastrear el costo)
- Puertos abiertos a `0.0.0.0/0` en security groups
- Hardcodear region, cuenta ID o access keys
- Aprobar `terraform apply` sin revisar `terraform plan`

From LeandroBenjaminL/lend-ai, MIT.

More from LeandroBenjaminL/lend-ai

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
May 10, 2026 (5 months ago)
Last release
May 16, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Leandro Benjamin L.

Cite this page

cloud-architect skill. Agent Mart. https://agentmart.dev/skills/leandrobenjaminl-cloud-architect (last updated 2026-10-24)