aws-serverless
Patterns and best practices for AWS serverless workloads. Use when the user asks about Lambda (cold starts, memory, concurrency, timeouts), Lambda Powertools (Logger, Tracer, Metrics), observability, CloudWatch alarms, event-driven architecture (SQS, SNS, EventBridge, Step Functions), or API Gateway (HTTP vs REST API, rate limiting, WAF, X-Ray tracing, going-live checklist). Triggers on: Lambda, cold start, Powertools, SQS, SNS, EventBridge, Step Functions, ECS vs Lambda, DLQ, event-driven, serverless, concurrency, provisioned concurrency, API Gateway, HTTP API, REST API, WAF, rate limiting.
82
85%
Does it follow best practices?
Impact
100%
1.56xAverage score across 2 eval scenarios
Low
Low-risk findings worth noting
Evaluation results
100%
52%Order Processing Pipeline — Terraform Infrastructure
SQS-Lambda order pipeline with DLQ and partial batch failure
Visibility timeout ratio
0%
100%
DLQ defined
100%
100%
DLQ alarm present
100%
100%
ReportBatchItemFailures in ESM
100%
100%
ReportBatchItemFailures in Lambda code
30%
100%
Lambda Errors alarm
0%
100%
Lambda Throttles alarm
0%
100%
Lambda Duration alarm
0%
100%
No CPU/memory alarms
100%
100%
Lambda transforms data
100%
100%
100%
20%Production-Ready Order Processing Lambda
Lambda observability with Powertools
Logger from Powertools
100%
100%
No print() calls
100%
100%
Powertools Metrics used
100%
100%
No direct CloudWatch API
100%
100%
Metrics decorator outermost
100%
100%
inject_lambda_context second
0%
100%
capture_lambda_handler innermost
100%
100%
add_metadata for order_id
0%
100%
No order_id as dimension
100%
100%
X-Ray active tracing
100%
100%
- Repository
- a-pavithraa/aws-serverless-skill
- Commit
2b66211
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.