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

73%

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

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

The body functions well as a progressive-disclosure overview that defers detailed steps to a real reference file, but it leans on the reference for most actionable guidance and carries a redundant Overview paragraph. Tightening the Overview and surfacing a couple more concrete commands would raise the score.

Suggestions

Trim or remove the Overview paragraph that restates the description's list of causes to avoid redundant padding and improve conciseness.

Add 1-2 more concrete, copy-paste-ready AWS CLI commands or log-query snippets in the Troubleshooting section rather than only deferring to the reference.

Inline a brief numbered step sequence (collect config -> metrics -> logs -> dependencies -> report) with an explicit verification checkpoint so the body itself conveys workflow clarity.

Dimension	Reasoning	Score
Conciseness	The Overview section restates the frontmatter description's list of causes nearly verbatim ('insufficient timeout settings, external service delays, database connection issues, memory constraints, and inefficient code patterns'), which is redundant padding; otherwise the body is reasonably lean, placing it at the score-3 anchor.	3 / 5
Actionability	Only one concrete command appears in the body ('aws lambda list-functions --region <region>'); most troubleshooting subsections defer with 'See the full procedure for details', so executable guidance is present but incomplete, fitting the score-3 anchor.	3 / 5
Workflow Clarity	The body summarizes the procedure's phases (config, metrics, logs, dependencies, cold starts, report) and directs to the reference, but no explicit step sequence or validation checkpoints appear in the body itself; this is a read-only investigation so the destructive-cap does not apply, landing at score 3.	3 / 5
Progressive Disclosure	The body is a clear overview pointing to a single, real one-level reference (references/lambda-timeout-debugging.md) with a well-signaled link; minor duplication of troubleshooting content between body and reference keeps it just below the score-5 anchor.	4 / 5
	Total	13 / 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 clearly communicates a specific AWS Lambda debugging capability with an explicit use-when trigger. It is comprehensive and distinctive, with only minor room to add a few more trigger synonyms.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete analysis domains ('function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream dependencies') with comprehensive coverage, matching the score-5 anchor.	5 / 5
Completeness	Explicitly states what it does ('Debugs... by systematically analyzing... to identify root causes with actionable fixes') and when to use it ('Use when a Lambda function is timing out or approaching its timeout limit'), satisfying the score-5 anchor for both what and when.	5 / 5
Trigger Term Quality	Natural phrases like 'Lambda function is timing out' and 'approaching its timeout limit' align with what users say, but a few synonyms (e.g. 'Lambda timeout error', 'function timeout') are absent, fitting just below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow, well-defined niche (AWS Lambda timeout debugging) with distinct triggers and minimal overlap with other skills, matching the score-5 anchor.	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: aws/agent-toolkit-for-aws
Path: skills/specialized-skills/serverless-skills/debugging-lambda-timeouts/SKILL.md
Commit: d6ad2e4

Reviewed: about 2 hours 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.