Agent skill · software engineering · sickn33
aws-serverless-eda
AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows.
Why this skill is useful
Provides specific AWS serverless architecture patterns and best practices that the AI wouldn't reliably generate on its own.
What it needs
Requires aws-cdk-development installed locally. Requires aws account access. About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
AWS Serverless & Event-Driven Architecture This skill provides comprehensive guidance for building serverless applications and event-driven architectures on AWS based on Well-Architected Framework principles. AWS Documentation Requirement Always verify AWS facts using MCP tools (mcpaws-mcp or mcpawsdocs) before answering. The aws-mcp-setup dependency is auto-loaded — if MCP tools are unavailable, guide the user through that skill's setup flow. Serverless MCP Servers This skill leverages the CDK MCP server (provided via aws-cdk-development dependency) and AWS Documentation MCP for serverless guidance. Note: The following AWS MCP servers are available separately via the Full AWS MCP Server (see aws-mcp-setup skill) and are not bundled with this plugin: - AWS Serverless MCP — SAM CLI lifecycle (init, deploy, local test) - AWS Lambda Tool MCP — Direct Lambda invocation - AWS Step Functions MCP — Workflow orchestration - Amazon SNS/SQS MCP — Messaging and queue management When to Use This Skill Use this skill when: Building serverless applications with Lambda Designing event-driven architectures Implementing microservices patterns Creating asynchronous processing workflows Orchestrating multi-service transactions Building real-time data processing pipelines Implementing saga patterns for distributed transactions Designing for scale and resilience AWS Well-Architected Serverless Design Principles 1. Speedy, Simple, Singular Functions should be concise and single-purpose Keep functions environmentally efficient and cost-aware: Minimize cold start times Optimize memory allocation Use provisioned concurrency only when needed Leverage connection reuse 2. Think Concurrent Requests, Not Total Requests Design for concurrency, not volume Lambda scales horizontally - design considerations should focus on: Concurrent execution limits Downstream service throttling Shared resource contention Connection pool sizing 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/aws-serverless-eda--120aad