tech-leads-club/aws-advisor
packages/skills-catalog/skills/(cloud)/aws-advisor/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add tech-leads-club/agent-skills aws-advisorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 5:15 AM8.5s9 files scanned
SKILL.md
- name:
- aws-advisor
- description:
- 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.
- license:
- CC-BY-4.0
- author:
- Felipe Rodrigues - github.com/felipfr
- version:
- 1.0.0
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
Related Skills
tech-leads-club/tlc-spec-driven
tools
VerifiedTrustedCommunity
Feature planning and implementation with 4 adaptive phases (Specify, Design, Tasks, Execute). Auto-sizes depth by complexity. Writes testable requirements in EARS notation, atomic tasks, atomic Conventional Commits, and requirement traceability. Ships deterministic Python validation scripts so structural gates are enforced by code, not memory. Features an independent Verifier (author != verifier, evidence-or-zero), a discrimination sensor, a decision log (STATE.md), a test-coverage matrix, and a self-improving lessons layer. Stack-agnostic and tool-agnostic. 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 design documents.
4,984SKILL.mdUpdated Apr 27, 2026
tech-leads-club/not-your-babysitter
tools
VerifiedTrustedCommunity
Autonomous senior-operator mode for AI agents that resolve tasks end to end without babysitting and never create new problems. The agent verifies every claim against real evidence (web search dated to the current month and year, the codebase, and available tools, MCPs, and CLIs); it never guesses, never fakes confidence, and never claims something is done without proof. It stays silent and keeps working, interrupting the user only on three stops, namely a destructive or irreversible action, a dead-end with no evidence after exhausting sources, or genuine ambiguity that changes the outcome. Output is short, literal, and human. Use when the user says "not-your-babysitter", "nanny mode", "work autonomously", "stop babysitting", or "no hand-holding", or wants an agent that solves problems on its own, especially hands-on engineering and operational tasks. Do not use when the user explicitly wants a tutorial, a verbose walkthrough, or open-ended brainstorming.
4,964SKILL.mdUpdated Aug 1, 2026
tech-leads-club/the-jury
development
VerifiedTrustedCommunity
Use when a question, decision, plan, tradeoff, or claim needs a rigorous verdict and one perspective is not enough. Spawns a panel of 3 to 5 subagent jurors that form independent blind opinions, deliberate anonymously under an anti-anchoring and anti-sycophancy protocol, and return one committed verdict with confidence, preserved dissent, and a concrete next action. Domain-agnostic across engineering, architecture, data, product, hiring, strategy, vendor choice, build-vs-buy, and research design. Trigger phrases include "convene a jury", "have agents debate and decide", "get a panel to decide", "multi-agent decision", "stress-test this and decide", "monte um juri", "tribunal de agentes", "painel para decidir". Do NOT use to only critique without deciding (use the-fool for that), to build a plan or write the solution itself, or for simple factual lookups.
4,964SKILL.mdUpdated Aug 1, 2026
tech-leads-club/evolutionary-modular-architecture
development
VerifiedTrustedCommunity
Guides design and implementation of evolutionary modular-monolith platforms with DDD (strategic + tactical), flat-by-aggregate organization, an Anti-Corruption Layer for vendor independence, a transactional outbox for events, smart resilience (backoff with jitter, circuit breakers, idempotency), and a polished architecture HTML document with elegant SVG diagrams. Use when designing a platform or backend, defining bounded contexts, organizing modules and folders, choosing monolith vs microservices, decoupling from an external service (ERP, storage, AI), making calls resilient, adding real-time push, picking a 2026 TypeScript stack (Nx, NestJS, React), or producing an architecture document or diagram. Also triggers on 'modular monolith', 'bounded contexts', 'flat-by-aggregate', 'ports and adapters', 'architecture diagram'. Do NOT use for simple CRUD, NestJS-only deep implementation (use nestjs-modular-monolith), or pure domain-model review (use tactical-ddd).
4,964SKILL.mdUpdated Aug 1, 2026