lambda

AWS Lambda serverless functions for event-driven compute. Use when creating functions, configuring triggers, debugging invocations, optimizing cold starts, setting up event source mappings, or managing layers.

1.10x

Quality

82%

Does it follow best practices?

Impact

96%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

64%

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

This is a comprehensive AWS Lambda reference with strong actionability—concrete CLI commands and Python code are its greatest strength. However, it's overly verbose for a skill file, explaining concepts Claude already knows (Lambda basics, invocation types, execution environment) and including CLI reference tables that duplicate built-in knowledge. The lack of validation checkpoints in multi-step workflows and the monolithic structure prevent it from scoring higher.

Suggestions

Remove the Core Concepts section entirely or reduce it to a one-line reminder—Claude already knows what Lambda functions, cold starts, and layers are.

Remove or drastically trim the CLI Reference tables, which duplicate information Claude already has access to.

Add explicit validation steps to multi-step workflows, e.g., after create-function run `aws lambda get-function --function-name MyFunction` to confirm creation before proceeding.

Split troubleshooting and best practices into separate referenced files (e.g., TROUBLESHOOTING.md, BEST_PRACTICES.md) to keep SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary content Claude already knows (e.g., explaining what Lambda is, what cold/warm starts are, what layers are). The CLI reference tables largely duplicate information Claude already has. The core concepts section and some best practices are padding, though the code examples themselves are lean.	2 / 3
Actionability	The skill provides fully executable CLI commands and Python code examples that are copy-paste ready. Every common pattern includes concrete, complete commands with realistic arguments and flags.	3 / 3
Workflow Clarity	While individual commands are clear, multi-step workflows lack explicit validation checkpoints. For example, the 'Create a Python Function' flow doesn't verify the function was created successfully before proceeding, and the layer creation/attachment flow has no validation step. Troubleshooting sections provide debug steps but no feedback loops for iterative fixing.	2 / 3
Progressive Disclosure	The content is a monolithic document with a table of contents but no splitting into separate files. The CLI reference tables, detailed troubleshooting, and best practices sections could be offloaded to separate referenced files. External references are provided at the end but only to AWS docs, not to bundle files.	2 / 3
	Total	9 / 12 Passed

Description

100%

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

This is a well-crafted skill description that concisely identifies the domain (AWS Lambda), lists specific capabilities, and provides explicit trigger guidance via a 'Use when...' clause. It uses third-person voice correctly and includes domain-specific terms that minimize conflict risk with other skills. The description is both comprehensive and concise.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: creating functions, configuring triggers, debugging invocations, optimizing cold starts, setting up event source mappings, and managing layers. These are distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (AWS Lambda serverless functions for event-driven compute) and 'when' with an explicit 'Use when...' clause listing six specific trigger scenarios.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Lambda', 'serverless', 'functions', 'triggers', 'cold starts', 'event source mappings', 'layers', 'invocations'. These cover common terms developers naturally use when working with AWS Lambda.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with AWS Lambda-specific terminology like 'cold starts', 'event source mappings', 'layers', and 'invocations' that clearly distinguish it from general cloud, serverless, or other AWS service skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: itsmostafa/aws-agent-skills
Commit: 4ab904a

Reviewed: about 1 month 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.