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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized serverless reference skill with strong progressive disclosure and concrete, actionable guidance. The main weak spots are the time-sensitive SnapStart version matrix and the duplicated OS-specific MCP config, which slightly dilute conciseness.

Suggestions

Move the SnapStart date/runtime matrix into the relevant reference file (e.g. lambda-patterns.md) or a dedicated 'version notes' section, since time-sensitive dates in the main body penalize conciseness.

Consolidate the macOS/Linux and Windows MCP config blocks into one config with a note about the Windows-only command/args variant to avoid near-duplicate JSON.

Add one short inline Lambda code snippet (e.g. a Powertools Logger/Tracer/Metrics example) in the body so the most common action is executable without opening a reference file.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — tables, 'Don't' bullets, and decision matrices assume Claude's knowledge with no padding — but the SnapStart Version Matrix carries time-sensitive dates (Nov 2021, Oct 2024) outside a deprecated section and the MCP config is duplicated across macOS/Linux and Windows, which could be trimmed.	4 / 5
Actionability	Concrete, executable guidance throughout: specific numeric rules ('set visibility timeout to 6x Lambda timeout'), decision tables, and a copy-paste-ready MCP JSON config. The gap is that actual Lambda code examples are deferred to references rather than shown inline.	4 / 5
Workflow Clarity	The Reference Loading Strategy is a clear, sequenced routing list mapping user queries to reference files, and the Cost Analysis gives ordered MCP setup steps. No validation checkpoints are needed for this routing/knowledge skill, so the sequence is clear with only minor gaps.	4 / 5
Progressive Disclosure	Excellent structure: a Quick Reference table and a Reference Loading Strategy give well-signaled, one-level-deep pointers to five real reference files (all present in references/), with detail appropriately split out of SKILL.md.	5 / 5
	Total	17 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description with explicit 'what' and 'when' guidance and a rich trigger term list. Minor improvements would be replacing the generic 'patterns and best practices' framing with concrete action verbs and qualifying the generic trigger terms with the AWS context.

Dimension	Reasoning	Score
Specificity	Lists many concrete sub-capabilities (cold starts, memory, concurrency, Powertools Logger/Tracer/Metrics, SQS/SNS/EventBridge/Step Functions, API Gateway HTTP vs REST, WAF, X-Ray), but the top-level action verb 'Patterns and best practices for...' is generic rather than naming explicit actions like configure, debug, or optimize.	4 / 5
Completeness	Clearly answers 'what' ('Patterns and best practices for AWS serverless workloads') and explicitly answers 'when' via both a 'Use when the user asks about...' clause and a 'Triggers on:' list with concrete trigger phrases.	5 / 5
Trigger Term Quality	An explicit 'Triggers on:' list provides comprehensive natural terms with synonyms (HTTP API / REST API / API Gateway; concurrency / provisioned concurrency) that users would actually say.	5 / 5
Distinctiveness Conflict Risk	The AWS serverless niche (Lambda, EventBridge, Step Functions) is distinct, but the raw trigger list includes generic terms like 'concurrency', 'rate limiting', 'WAF', and 'observability' without AWS qualification, creating minor overlap risk with non-AWS skills.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: a-pavithraa/aws-serverless-skill
Path: skills/aws-serverless/SKILL.md
Commit: 2b66211

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.