agentsclimarketplace

Aws serverless

Skill a-pavithraa/aws-serverless-skill/skills/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.From its SKILL.md

Install
npx -y skills add a-pavithraa/aws-serverless-skill --skill aws-serverless

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.2 KB, as published. Nobody here has run it

AWS Serverless

Quick Reference

TopicReference FileKey Insight
Lambda internalsreferences/lambda-patterns.mdCold start happens per concurrent execution, not just once
Lambda Layersreferences/lambda-patterns.mdDeployment optimization, NOT a package manager
Observabilityreferences/lambda-powertools.mdUse Powertools for Logger, Tracer, Metrics — never print()
Monitoring/alarmsreferences/monitoring.mdAlert on symptoms (errors, latency), not causes (CPU)
Event-drivenreferences/event-driven.mdSingle Lambda vs Step Functions decision; Standard/Express/Hybrid; Saga pattern
API Gatewayreferences/api-gateway.mdHTTP API ~70% cheaper; use REST API only for WAF/caching/usage plans

Critical Anti-Patterns

Lambda

  • Don't assume cold start is "just the first request" — it happens per concurrent execution
  • Don't use Lambda Layers as a package manager — use them for deployment optimization only
  • Don't call Lambda synchronously from Lambda — use SQS, SNS, or Step Functions
  • Don't set user-facing API timeout to 30s ; use async for long operations

Observability

  • Don't use print() for logging — use Powertools Logger for structured JSON
  • Don't call CloudWatch API synchronously for metrics — use Powertools Metrics (EMF format)
  • Don't alert on resource utilization (CPU, memory) — alert on user-impacting symptoms

Event-Driven

  • Don't set SQS visibility timeout shorter than Lambda timeout — set it to 6× Lambda timeout
  • Don't omit a DLQ — always pair queues with a DLQ and alarm on it
  • Don't use Lambda to transport data between services — use direct integrations; reserve Lambda for transforming data

"Use Lambda to transform data, not to transport data between services." — Jérôme Van Der Linden

Decision Frameworks

Lambda vs Step Functions

Use Lambda WhenUse Step Functions When
Single operation < 15 minsWorkflow with multiple steps
Simple request-responseNeed retry/error handling per step
Stateless processingLong-running or human-in-loop
Visual workflow debugging needed

Lambda vs ECS

Use Lambda WhenUse ECS When
Execution < 15 minutesLong-running processes
Bursty, unpredictable trafficSteady, high-volume traffic
Cold start acceptableSub-100ms latency required
Pay-per-invocation preferredNeed GPU or special hardware

Cost Analysis

When the user asks about cost impact or reducing costs for Lambda, SQS, SNS, EventBridge, or Step Functions, direct them to install the AWS Pricing MCP Server. It provides real-time pricing data and cost optimisation recommendations via get_pricing and generate_cost_report.

Prerequisites: uv package manager, Python 3.10+, AWS credentials with pricing:* permissions.

macOS / Linux:

{
  "mcpServers": {
    "awslabs.aws-pricing-mcp-server": {
      "command": "uvx",
      "args": ["awslabs.aws-pricing-mcp-server@latest"],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_PROFILE": "your-aws-profile",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Windows:

{
  "mcpServers": {
    "awslabs.aws-pricing-mcp-server": {
      "command": "uvx",
      "args": [
        "--from", "awslabs.aws-pricing-mcp-server@latest",
        "awslabs.aws-pricing-mcp-server.exe"
      ],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_PROFILE": "your-aws-profile",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

Add the above to ~/.claude/claude_desktop_config.json (Claude Desktop) or .claude/mcp.json (Claude Code) under mcpServers.


Version Matrix

FeatureAWS GASupported Runtimes
SnapStartNov 2021 (Java); Oct 2024 (Python, .NET)Java 11+, Python 3.12+, .NET 8+ — not Node, Ruby, or container images

Reference Loading Strategy

Load references based on what the user is asking:

  1. Cold starts, memory tuning, concurrency, Layers → references/lambda-patterns.md
  2. Logging, tracing, metrics, Powertools setup → references/lambda-powertools.md
  3. CloudWatch alarms, dashboards, alerting strategy → references/monitoring.md
  4. SQS, SNS, EventBridge, Step Functions, Saga → references/event-driven.md
  5. API Gateway (HTTP vs REST, going-live checklist, WAF, X-Ray, security) → references/api-gateway.md

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.