aws-lambda-best-practices

AWS Lambda best practices for function design, configuration, and operations. Use when designing Lambda functions, choosing memory/timeout settings, planning concurrency and scaling, setting up monitoring, processing streams, or securing Lambda workloads. Triggers on tasks involving Lambda function creation, handler design, cold start optimization, idempotency, event source mapping, reserved/provisioned concurrency, or deciding whether Lambda is the right compute choice. Does not cover language-specific SDK patterns, CloudFormation/Terraform resource definitions, or Lambda@Edge.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%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-structured, token-efficient reference with excellent progressive disclosure and strong actionability through specific numbers and tools. Its main gap is the absence of explicit validation checkpoints and copy-paste code, which limits workflow clarity and top-tier actionability.

Suggestions

Add one or two copy-paste-ready code snippets (e.g., a minimal idempotent handler skeleton or an EMF/Powertools logging example) to lift actionability from concrete guidance to fully executable.

Add an explicit validate→fix→retry loop for stream/batch operations (e.g., after enabling ReportBatchItemFailures, verify the partial-batch response shape and test retry behavior) so workflow_clarity is not capped at 3.

Include a short sequenced 'design → configure → deploy → verify' checklist with checkpoints to convert the topic-organized reference into a clear procedural workflow.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout — tables convey limits and recommendations compactly, and it never explains concepts Claude already knows (no 'what is Lambda/DynamoDB' padding); every section earns its tokens.	5 / 5
Actionability	Concrete thresholds and tools throughout ('1,769 MB' for one vCPU, 'p99 duration + 20-50% buffer', 'SQS Visibility Timeout >= 6x function timeout', the Power Tuning link), but as an instruction-only conventions doc it lacks copy-paste-ready code examples, keeping it just below the top anchor.	4 / 5
Workflow Clarity	Content is topic-organized (fit → design → configure → scale → monitor → streams → security) rather than a sequenced procedural workflow, and batch/stream operations lack an explicit validate→fix→retry feedback loop, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Clear overview body with well-signaled one-level-deep references — each section ends with 'See references/X.md for...' and a 'Reference Files' section lists all seven files, each verified present in ./references/, with no nested reference chains.	5 / 5
	Total	17 / 20 Passed

Description

100%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.

An excellent description: third-person, concise, and comprehensive, clearly stating what the skill covers, when to use it, and where its boundaries lie. Every dimension matches the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'function design, configuration, and operations', 'designing Lambda functions, choosing memory/timeout settings, planning concurrency and scaling, setting up monitoring, processing streams, or securing Lambda workloads' — giving comprehensive coverage rather than vague phrasing.	5 / 5
Completeness	Explicitly answers both 'what' ('AWS Lambda best practices for function design, configuration, and operations') and 'when' ('Use when designing Lambda functions...'), plus a concrete trigger list and explicit exclusions.	5 / 5
Trigger Term Quality	Comprehensive natural terms users would say — 'Lambda functions', 'memory/timeout settings', 'concurrency and scaling', 'cold start optimization', 'idempotency', 'event source mapping', 'reserved/provisioned concurrency' — including synonyms and variations.	5 / 5
Distinctiveness Conflict Risk	Clear Lambda-specific niche with distinct triggers and explicit boundary ('Does not cover language-specific SDK patterns, CloudFormation/Terraform resource definitions, or Lambda@Edge'), minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: provectus/awos-recruitment
Path: registry/skills/aws-lambda-best-practices/SKILL.md
Commit: 298fce7

Reviewed: 4 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.