debugging-lambda-timeouts

Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream dependencies to identify root causes with actionable fixes. Use when a Lambda function is timing out or approaching its timeout limit.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/specialized-skills/serverless-skills/debugging-lambda-timeouts/SKILL.md

Quality

Content

57%

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

The body is a clean, well-organized overview with excellent progressive disclosure via a single one-level-deep reference. It is weakest on in-body actionability and workflow detail because the executable steps and validation checkpoints are delegated to the reference file rather than surfaced here.

Suggestions

Trim the Overview's redundant enumeration of data sources and causes (already covered by the description) so the body adds only what the description does not.

Surface one or two key executable commands inline — e.g., the CloudWatch Logs Insights query or the get-function-configuration call — so the body is actionable without opening the reference.

Briefly inline the procedure's core validation gates (verify dependencies / confirm required parameters before proceeding) so the workflow's checkpoints are visible in SKILL.md, not only in the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the Overview re-enumerates the same data sources and a list of causes ('insufficient timeout settings, external service delays, database connection issues, memory constraints...') that overlaps the description, which is mild padding Claude could infer.	2 / 3
Actionability	Concrete executable guidance in the body is limited to one command ('aws lambda list-functions --region <region>'); the rest ('Check the function's log group configuration', 'See the full procedure for details') is direction rather than copy-paste-ready instruction, with the actual commands living in the reference.	2 / 3
Workflow Clarity	A high-level sequence is present (Overview -> Debug procedure -> Troubleshooting) and it directs the reader to 'follow the procedure exactly', but the validation checkpoints and step ordering live in the reference file rather than the body, leaving checkpoints implicit here.	2 / 3
Progressive Disclosure	A clear overview points to a single well-signaled one-level-deep reference '[Lambda timeout debugging procedure](references/lambda-timeout-debugging.md)'; that reference contains no nested references, and content is appropriately split between SKILL.md and the reference.	3 / 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.

A well-crafted description: specific, third-person, with an explicit trigger and a narrow, distinguishable niche. It scores at the top of every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream dependencies to identify root causes with actionable fixes' — matching the score-3 anchor.	3 / 3
Completeness	Clearly answers both 'what' (debugs Lambda timeout failures by analyzing specific sources) and 'when' via the explicit trigger 'Use when a Lambda function is timing out or approaching its timeout limit.'	3 / 3
Trigger Term Quality	Natural terms a user would say are present: 'Lambda function is timing out' and 'approaching its timeout limit', giving good coverage of common phrasings rather than generic jargon.	3 / 3
Distinctiveness Conflict Risk	The niche is narrowly scoped to AWS Lambda timeouts with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: aws/agent-toolkit-for-aws
Path: skills/specialized-skills/serverless-skills/debugging-lambda-timeouts/SKILL.md
Commit: 222ce56

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