When your Lambda hits timeout and you're digging through CloudWatch logs trying to figure out why, this walks you through a systematic investigation. It checks the obvious stuff like timeout configuration and memory settings, then digs into cold starts, VPC networking issues, downstream dependencies, and code patterns that burn through execution time. The structured procedure keeps you from randomly guessing or missing something critical when you're under pressure to fix it. Most useful when you're dealing with intermittent timeouts or inheriting someone else's Lambda that's mysteriously slow, since it forces you to look at metrics and logs in a specific order rather than just bumping the timeout and hoping.
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts