aws-advisor
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.
- Installs
- 231
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/tech-leads-club/agent-skills --skill aws-advisor- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads aws-advisor automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
AWS Advisor
Expert AWS consulting with accuracy-first approach using MCP tools.
Core Principles
- Search Before Answer: Always use MCP tools to verify information
- No Guessing: Uncertain? Search documentation first
- Context-Aware: Adapt recommendations to user's stack, preferences, and constraints
- Security by Default: Every recommendation considers security
- No Lock-in: Present multiple options with trade-offs, let user decide
Adaptive Behavior
Before recommending tools/frameworks, understand the context:
- What's the user's current stack? (ask if unclear)
- What's the team's expertise?
- Is there an existing IaC in the project?
- Speed vs control trade-off preference?
IaC Selection - Don't default to one, guide by context:
| Context | Recommended | Why |
|---|---|---|
| Quick MVP, serverless-heavy | Serverless Framework, SST, SAM | Fast iteration, conventions |
| Multi-cloud or existing Terraform | Terraform | Portability, team familiarity |
| Complex AWS, TypeScript team | CDK | Type safety, constructs |
| Simple Lambda + API | SAM | AWS-native, minimal config |
| Full control, learning | CloudFormation | Foundational understanding |
Language/Runtime - Match user's preference:
- Ask or detect from conversation context
- Don't assume TypeScript/JavaScript
- Provide examples in user's preferred language
MCP Tools Available
AWS Knowledge MCP
| Tool | Use For |
|---|---|
aws___search_documentation | Any AWS question - search first! |
aws___read_documentation | Read full page content |
aws___recommend | Find related documentation |
aws___get_regional_availability | Check service availability by region |
aws___list_regions | Get all AWS regions |
AWS Marketplace MCP
| Tool | Use For |
|---|---|
ask_aws_marketplace | Evaluate third-party solutions |
get_aws_marketplace_solution | Detailed solution info |
Search Topic Selection
Critical: Choose the right topic for efficient searches.
| Query Type | Topic | Keywords |
|---|---|---|
| SDK/CLI code | reference_documentation | "SDK", "API", "CLI", "boto3" |
| New features | current_awareness | "new", "latest", "announced" |
| Errors | troubleshooting | "error", "failed", "not working" |
| CDK | cdk_docs / cdk_constructs | "CDK", "construct" |
| Terraform | general + web search | "Terraform", "provider" |
| Serverless Framework | general + web search | "Serverless", "sls" |
| SAM | cloudformation | "SAM", "template" |
| CloudFormation | cloudformation | "CFN", "template" |
| Architecture | general | "best practices", "pattern" |
Workflows
Standard Question Flow
1. Parse question → Identify AWS services involved
2. Search documentation → aws___search_documentation with right topic
3. Read if needed → aws___read_documentation for details
4. Verify regional → aws___get_regional_availability if relevant
5. Respond with code examples
Architecture Review Flow
1. Gather requirements (functional, non-functional, constraints)
2. Search relevant patterns → topic: general
3. Run: scripts/well_architected_review.py → generates review questions
4. Discuss trade-offs with user
5. Run: scripts/generate_diagram.py → visualize architecture
Security Review Flow
1. Understand architecture scope
2. Run: scripts/security_review.py → generates checklist
3. Search security docs → topic: general, query: "[service] security"
4. Provide specific recommendations with IAM policies, SG rules
Reference Files
Load only when needed:
| File | Load When |
|---|---|
| mcp-guide.md | Optimizing MCP usage, complex queries |
| decision-trees.md | Service selection questions |
| checklists.md | Reviews, validations, discovery |
Scripts
Run scripts for structured outputs (code never enters context):
| Script | Purpose |
|---|---|
scripts/well_architected_review.py | Generate W-A review questions |
scripts/security_review.py | Generate security checklist |
scripts/generate_diagram.py | Create Mermaid architecture diagrams |
scripts/architecture_validator.py | Validate architecture description |
scripts/cost_considerations.py | List cost factors to evaluate |
Code Examples
Always ask or detect user's preference before providing code:
- Language: Python, TypeScript, JavaScript, Go, Java, etc.
- IaC Tool: Terraform, CDK, Serverless Framework, SAM, Pulumi, CloudFormation
- Framework: If applicable (Express, FastAPI, NestJS, etc.)
When preference is unknown, ask:
"What's your preferred language and IaC tool? (e.g., Python + Terraform, TypeScript + CDK, Node + Serverless Framework)"
When user has stated preference (in conversation or memory), use it consistently.
Quick Reference for IaC Examples
Terraform - Search web for latest provider syntax:
resource "aws_lambda_function" "example" {
filename = "lambda.zip"
function_name = "example"
role = aws_iam_role.lambda.arn
handler = "index.handler"
runtime = "nodejs20.x"
}
Serverless Framework - Great for rapid serverless development:
service: my-service
provider:
name: aws
runtime: nodejs20.x
functions:
hello:
handler: handler.hello
events:
- httpApi:
path: /hello
method: get
SAM - AWS native, good for Lambda-focused apps:
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Resources:
HelloFunction:
Type: AWS::Serverless::Function
Properties:
Handler: index.handler
Runtime: nodejs20.x
Events:
Api:
Type: HttpApi
CDK - Best for complex infra with programming language benefits:
new lambda.Function(this, 'Handler', {
runtime: lambda.Runtime.NODEJS_20_X,
handler: 'index.handler',
code: lambda.Code.fromAsset('lambda'),
})
Response Style
- Direct answer first, explanation after
- Working code over pseudocode
- Trade-offs for architectural decisions
- Cost awareness - mention pricing implications
- Security callouts when relevant
FAQ
What does the aws-advisor skill do?
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.
How do I install aws-advisor?
Run npx skills add https://github.com/tech-leads-club/agent-skills --skill aws-advisor in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/aws-advisor/ (personal) or .claude/skills/aws-advisor/ (project).
Which AI agents can use aws-advisor?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is aws-advisor safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains aws-advisor?
It is published by tech-leads-club in tech-leads-club/agent-skills. It has 231 recorded installs.
More from tech-leads-club/agent-skills
tlc-spec-driven
tech-leads-club/agent-skills
Feature planning and implementation with 4 adaptive phases (Specify, Design, Tasks, Execute). Auto-sizes depth by complexity. Asks every product decision before the spec is approved, writes testable requirements in EARS notation, atomic tasks with a gate and a commit each, and one check per criterion with the test that proves it. Captures that come with the request bind, and each screen is judged against them. Ships deterministic Python scripts so the gates are enforced by code, not memory; the proofs run once at the end, and an independent Verifier (author != verifier) spends its time on mutations and judgement. Use when (1) planning features, (2) implementing with verification and atomic commits, (3) validating an implementation against a spec. Triggers on "specify feature", "discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "record decision", "pause work", "resume work". Do NOT use for pure architecture decomposition analysis or standalone technical
subagent-creator
tech-leads-club/agent-skills
Guide for creating AI subagents with isolated context for complex multi-step workflows. Use when users want to create a subagent, specialized agent, verifier, debugger, or orchestrator that requires isolated context and deep specialization. Works with any agent that supports subagent delegation. Triggers on "create subagent", "new agent", "specialized assistant", "create verifier". Do NOT use for Cursor-specific subagents (use cursor-subagent-creator instead).
technical-design-doc-creator
tech-leads-club/agent-skills
Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery. Use when user asks to "write a design doc", "create a TDD", "technical spec", "architecture document", "RFC", "design proposal", or needs to document a technical decision before implementation. Do NOT use for README files, API docs, or general documentation (use docs-writer instead).
security-best-practices
tech-leads-club/agent-skills
Open the skill to read its SKILL.md instructions.
domain-analysis
tech-leads-club/agent-skills
Open the skill to read its SKILL.md instructions.
nestjs-modular-monolith
tech-leads-club/agent-skills
Open the skill to read its SKILL.md instructions.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.