Debugging lambda timeouts

Skill mouadja02/skills/skills/cloud-aws/serverless/debugging-lambda-timeouts

A curated collection of agent skills for your AI agents - engineering craft, prompt engineering, design, growth marketing, ...

Install

npx -y skills add mouadja02/skills --skill debugging-lambda-timeouts

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 296 tokens by cl100k_base, as published. Nobody here has run it

Debugging Lambda Timeouts

Overview

Domain expertise for systematically investigating AWS Lambda function timeout failures by analyzing function configuration, CloudWatch logs, metrics, dependencies, cold start patterns, and code. Identifies common causes such as insufficient timeout settings, external service delays, database connection issues, memory constraints, and inefficient code patterns, then provides prioritized recommendations.

Debug a Lambda timeout

To investigate and resolve Lambda timeout issues, follow the procedure exactly. See Lambda timeout debugging procedure.

The procedure collects function configuration, CloudWatch metrics and logs, dependency analysis, and cold start patterns. If Lambda code is provided, it also reviews the code for timeout-prone patterns. Results are compiled into a structured debugging report with prioritized recommendations.

Troubleshooting

Function not found

Verify the function name and region. Use aws lambda list-functions --region <region> to list available functions.

No logs available

The function may not have been invoked recently or logging may be disabled. Check the function's log group configuration and invocation metrics.

Access denied errors

Verify AWS credentials have permissions for Lambda, CloudWatch Logs, and CloudWatch Metrics. See the full procedure for details.

Log query time range issues

If CloudWatch Logs Insights queries fail with time range errors, reduce the analysis window or check log group retention settings. See the full procedure for details.