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

87%

Does it follow best practices?

Impact

96%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

82%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, highly actionable Lambda reference packed with executable CLI and boto3 examples and useful troubleshooting feedback loops. It is slightly held back by introductory concept padding and a monolithic single-file structure that could split its CLI reference into a bundled file.

Suggestions

Trim the marketing-style intro paragraph, the redundant Table of Contents, and the Core Concepts definitions of handler/context/cold-start that Claude already knows, to improve token efficiency.

Move the four CLI Reference tables into a bundled references/ file (e.g. cli-reference.md) and link to it one level deep, keeping only the most common commands inline in Common Patterns.

Add explicit validation checkpoints to the operational recipes (e.g., after create-function, run 'aws lambda get-function-configuration' to confirm state) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly lean reference material (compact tables, copy-paste code, terse bullets), but the marketing-style intro ('runs code without provisioning servers... scales from a few requests per day to thousands per second'), the redundant Table of Contents, and Core Concepts definitions of handler/context/cold-start over-explain what Claude already knows; not 5 because these tokens don't all earn their place.	4 / 5
Actionability	Fully executable AWS CLI and boto3 examples covering creation, update, invocation, triggers, event-source mappings, layers, and env vars are copy-paste ready and cover the common cases, matching the top anchor.	5 / 5
Workflow Clarity	Recipes are sequenced (zip -> create -> update) and Troubleshooting sections give Symptom -> Causes -> Debug -> Fix feedback loops; not 5 because the operational deploy/trigger patterns lack explicit validation checkpoints (e.g., no 'verify the function was created' step).	4 / 5
Progressive Disclosure	Good structure with a Table of Contents and clear section headers making navigation easy; not 5 because the full CLI reference and troubleshooting material are inlined in a ~340-line single file with no bundle files to offload bulk that could live one level deep.	4 / 5
	Total	17 / 20 Passed

Description

92%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, third-person description that explicitly pairs what the skill does with a concrete 'Use when' trigger clause listing six specific actions. Trigger-term coverage is broad but omits a few common phrasings users would naturally say.

Dimension	Reasoning	Score
Specificity	Lists six concrete actions ('creating functions, configuring triggers, debugging invocations, optimizing cold starts, setting up event source mappings, or managing layers'), matching the comprehensive-coverage anchor; not 4 because coverage spans the full Lambda lifecycle without notable gaps.	5 / 5
Completeness	Explicitly states what ('AWS Lambda serverless functions for event-driven compute') and when ('Use when creating functions, configuring triggers, debugging invocations, optimizing cold starts, setting up event source mappings, or managing layers') with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Good natural-term coverage ('triggers', 'invocations', 'cold starts', 'event source mappings', 'layers', 'serverless'), but common variations users say like 'deploy', 'timeout', 'logs', and 'runtime/handler' are absent, so it falls short of the comprehensive-synonym anchor.	4 / 5
Distinctiveness Conflict Risk	AWS Lambda is a clearly bounded service niche with distinct triggers, posing minimal conflict risk with other skills.	5 / 5
	Total	19 / 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: itsmostafa/aws-agent-skills
Path: skills/lambda/SKILL.md
Commit: e786d25

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.