AGENT SKILL

aws-specialist

Deep-dive AWS architecture review, debugging, and service design. Use for structured investigations of AWS-specific issues, cost or IAM audits, and multi-service design reviews. Triggers on: "AWS audit", "AWS design review", "IAM review", "cost audit AWS", "review my VPC", "AWS troubleshooting", "Lambda deep-dive".

使用场景视觉设计
License 许可
MIT
最近更新
2026-10-26
Stars
★ 0
Forks
0

01 前言 Front Matter

id
aws-specialist
name
aws-specialist
task
[ "debugging", "review" ]
type
skill
model
opus
owner
@kaiohenricunha
tools
Read, Grep, Glob, Bash
domain
[ "infra" ]
effort
max
created
1735689600000
updated
1776384000000
version
1.0.0
dotbabel
{ "compute": { "mode": "dynamic", "binding": "consumer", "rationale": "Evidence-based investigation or evaluation must hold several technical constraints at once.", "requirement": "deep" } }
maturity
validated
platform
[ "aws" ]
description
Deep-dive AWS architecture review, debugging, and service design. Use for structured investigations of AWS-specific issues, cost or IAM audits, and multi-service design reviews. Triggers on: "AWS audit", "AWS design review", "IAM review", "cost audit AWS", "review my VPC", "AWS troubleshooting", "Lambda deep-dive".
allowed-tools
Read Grep Glob Bash
argument-hint
<account context, service, or problem description>

02 资源文件 7

03 SKILL.md 正文

AWS Specialist

Structured investigation for AWS workloads. Five phases: gather context, diagnose, design, recommend, verify.

Arguments

  • $0 — account context, service scope, or problem description. Required.

Phase 1: Context Gathering

  1. Identify the account(s), region(s), and services in scope.
  2. Glob for IaC in the working directory: **/*.tf, **/*.yaml (SAM/CloudFormation), **/cdk.json, **/template.yaml.
  3. If AWS CLI access is available:
    aws sts get-caller-identity
    aws configure list
    
  4. Note the service scope (e.g. "EKS cluster + VPC + IAM" vs "Lambda + API Gateway + DynamoDB"). Scope commands to the relevant resource types.

Phase 2: Diagnosis

Compute / containers:

aws ec2 describe-instances --filters Name=instance-state-name,Values=running
aws ecs list-services --cluster <name>
aws eks describe-cluster --name <name>

IAM / identity:

aws iam list-policies --scope Local
aws iam get-role --role-name <role>
aws iam simulate-principal-policy --policy-source-arn <arn> --action-names <action>

Networking:

aws ec2 describe-vpcs
aws ec2 describe-route-tables
aws ec2 describe-security-groups

Serverless / events:

aws lambda list-functions
aws lambda get-function-configuration --function-name <name>
aws apigateway get-rest-apis

Cost / quotas:

aws service-quotas list-service-quotas --service-code ec2
aws ce get-cost-and-usage --time-period Start=<>,End=<> --granularity DAILY --metrics UnblendedCost

Phase 3: Design / Root-Cause Analysis

Map symptoms to causes:

Symptom Common Causes Check
5xx from ALB Unhealthy targets, timeout mismatch, HTTP/S misrouting Target group health, ALB access logs
Lambda throttled Reserved concurrency, account-wide limit aws lambda get-function-concurrency
EKS pod IAM fails Missing IRSA, ServiceAccount annotation OIDC provider + trust policy on role
S3 AccessDenied Bucket policy, SCP, VPC endpoint policy Use aws s3api get-bucket-policy + IAM simulator
RDS CPU spike Missing indexes, connection storm, runaway query Performance Insights, slow query log
CloudFront caching miss Incorrect cache key, missing Cache-Control Check behaviors + origin headers

Cite resource ARN or file:line for every finding.


Phase 4: Recommendations

Output findings in priority order:

[CRITICAL] <title>
Resource: <ARN or file:line>
Issue: <one sentence>
Evidence: <CLI output or code snippet>
Fix: <specific change, with IaC diff if applicable>
Trade-off: <alternative and its downside, if meaningful>
  • Order: CRITICAL → WARNING → INFO.
  • For IaC fixes, show the exact Terraform/CDK/CloudFormation diff.
  • Reference relevant docs in references/ where applicable.

Phase 5: Verification

After fixes are applied:

  1. Re-run the diagnostic command that surfaced the issue.
  2. For IAM changes: aws iam simulate-principal-policy with the exact action and resource.
  3. For networking changes: aws ec2 describe-route-tables or VPC Reachability Analyzer.
  4. For serverless changes: invoke a test event via aws lambda invoke or API Gateway test console.
  5. Check CloudWatch metrics and alarms — no new alarms should be triggering.

Reference Docs

Consult references/ for decision guides:

File When to use
compute.md EC2, ECS, EKS selection and sizing
serverless.md Lambda, API Gateway, EventBridge, SQS, SNS
storage.md S3, EBS, EFS, RDS, DynamoDB
networking.md VPC, ALB/NLB, Route53, CloudFront, PrivateLink
iam.md Policies, roles, SCPs, permission boundaries
observability.md CloudWatch, X-Ray, Container Insights
iac-patterns.md CloudFormation, CDK, SAM patterns

04 同仓库更多 Skills

kaiohenricunha
kaiohenricunha/dotbabel

yolo

Start temporary autonomy for the current task or an explicit scope with a required --for expiry. Codex permits scoped pushes, merges, deploys, and releases after strict testing and validation; Full access is a separate runtime setting. Claude Code uses a session permission hook with a protected-action denylist.

开发工程师
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

veracity-audit

Audit a data pipeline for Veracity and Value. Dispatches data-scientist, compliance-auditor, and data-engineer agents with project context injected at dispatch time. All source paths are supplied via flags — no defaults, no project assumptions. Subcommands: audit (full pipeline walk), score-check (scoring math only), gate-check (gate coverage only), source-trace <label> (single source end-to-end). Invoke when: "audit pipeline", "veracity check", "scoring math correct?", "check gates", "trace source", "verify quality gates", "formula correct?".

律师与法务Skill与智能体开发
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

validate-spec

Audit an already-implemented spec against the codebase. Walks each constraint (ARCH-N, PERF-N, KD-N, etc.) and acceptance criterion, grounds findings in file:line evidence, runs the spec.json acceptance_commands, and writes a single audit doc to docs/audits/. Use whenever the user asks to "validate a spec", "audit a spec", "check if spec is implemented", "verify the spec is done", "is this spec really done", or otherwise wants closure on spec-driven work. Read-only against the spec — produces an audit, never modifies the spec itself.

★ 0
kaiohenricunha
kaiohenricunha/dotbabel

terragrunt-specialist

Deep-dive Terragrunt hierarchy review, DRY pattern audits, and run-all orchestration analysis. Use for structured investigations of multi-environment Terragrunt layouts, dependency graphs, remote state config, and hook correctness. Triggers on: "Terragrunt audit", "run-all review", "dependency block", "DRY pattern review", "env hierarchy audit", "mock_outputs", "terragrunt hooks".

运维与部署
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

terraform-specialist

Deep-dive Terraform architecture review, module design, state management, and migration. Use for structured investigations of Terraform workspaces, provider configuration, module coupling, import workflows, and test coverage. Triggers on: "Terraform audit", "module review", "state management", "Terraform import", "workspace design", "provider config review", "Terraform testing".

测试与质量运维与部署
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

spec

Create structured engineering specs through interactive pairing. Use when the user wants to create a spec, design doc, technical specification, architecture document, RFC, or engineering plan. Triggers on "let's spec this out", "create a spec", "design doc", "write a technical plan", "plan the architecture". Works for greenfield and brownfield projects. Outputs to docs/specs/.

设计师视觉设计
★ 0