CRM Production Investigation Guidelines
aws/tools-for-devops-agent
Guidelines for investigating production incidents in the CRM application.
Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream…
Install Debugging Lambda Timeouts
$ npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/agent-toolkit-for-aws debugging-lambda-timeouts --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts .claude/skills/debugging-lambda-timeouts && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debugging-lambda-timeouts" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts into .claude/skills/debugging-lambda-timeouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-lambda-timeouts", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/debugging-lambda-timeoutsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/agent-toolkit-for-aws debugging-lambda-timeouts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts .agents/skills/debugging-lambda-timeouts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-lambda-timeouts" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts into .agents/skills/debugging-lambda-timeouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-lambda-timeouts", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/agent-toolkit-for-aws debugging-lambda-timeouts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts .cursor/skills/debugging-lambda-timeouts && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debugging-lambda-timeouts" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts into .cursor/skills/debugging-lambda-timeouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-lambda-timeouts", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws/agent-toolkit-for-aws.git --path skills/specialized-skills/serverless-skills/debugging-lambda-timeouts--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/agent-toolkit-for-aws debugging-lambda-timeouts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts .gemini/skills/debugging-lambda-timeouts && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debugging-lambda-timeouts" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts into .gemini/skills/debugging-lambda-timeouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-lambda-timeouts", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws/agent-toolkit-for-aws debugging-lambda-timeoutsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts .github/skills/debugging-lambda-timeouts && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debugging-lambda-timeouts" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts into .github/skills/debugging-lambda-timeouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-lambda-timeouts", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws/agent-toolkit-for-aws debugging-lambda-timeouts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts .opencode/skills/debugging-lambda-timeouts && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debugging-lambda-timeouts" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts into .opencode/skills/debugging-lambda-timeouts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-lambda-timeouts", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debugging-lambda-timeouts- GitHub stars
- 2.8k
- Token cost
- ~502 tokens
- SKILL.md length
- 207 words
- Files
- 2 (incl. references)
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream…
- A Lambda function is timing out
- SKILL.md covers Overview, Debug a Lambda timeout and Troubleshooting
- Calls aws
- Approaching its timeout limit
What it does
Debugging Lambda Timeouts is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. 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.
Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/lambda-timeout-debugging.md`).
It sits in Development, covering Serverless, Debugging and Root cause analysis. It works with AWS Lambda and Amazon Web Services. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.
When your agent uses it
- A Lambda function is timing out
- Approaching its timeout limit
Example prompts
- “Use the debugging-lambda-timeouts skill to debug AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch…”
- “/debugging-lambda-timeouts”
What it can do on your machine
Read from SKILL.md and the folder at commit 188af2f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
aws
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debugging Lambda Timeouts loads about 502 tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 207 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws/agent-toolkit-for-aws at commit 188af2f, republished under its Apache-2.0 licence (© aws). 207 words, ~502 tokens.
Download SKILL.mdSave it as
.claude/skills/debugging-lambda-timeouts/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- debugging-lambda-timeouts
- description
- 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.
- version
- 1
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.
© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/specialized-skills/serverless-skills/debugging-lambda-timeouts of aws/agent-toolkit-for-aws.
- SKILL.md
- references/lambda-timeout-debugging.md
Open the folder on GitHubat commit 188af2f
Compare with similar skills
Debugging Lambda Timeouts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debugging Lambda Timeouts this skillaws/agent-toolkit-for-aws | 2.8k | — | ~502 | Automated safety check: Pass | Apache-2.0 | |
| CRM Production Investigation Guidelinesaws/tools-for-devops-agent | 100 | — | ~983 | Automated safety check: Pass | Apache-2.0 | |
| AWS Sam Bootstrapgiuseppe-trisciuoglio/developer-kit | 355 | — | ~954 | Automated safety check: Notes | MIT | |
| AWS Serverless Edazxkane/aws-skills | 367 | 4 repos | ~3.2k | Automated safety check: Pass | MIT | |
| AWS Serverlessdavila7/claude-code-templates | 32k | 8 repos | ~2k | Automated safety check: Pass | MIT | |
| AWS Lambda Microvmsawslabs/agent-plugins | 915 | 1 repos | ~4.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
AWS Sam Bootstrap
giuseppe-trisciuoglio/developer-kit
Provides AWS SAM bootstrap patterns: generates template.yaml and samconfig.toml for new projects via sam init, creates SAM templates for existing Lambda/CloudFormation code migration, validates…
AWS Serverless Eda
zxkane/aws-skills
AWS serverless and event-driven architecture expert based on Well-Architected Framework.
AWS Serverless
davila7/claude-code-templates
Specialized skill for building production-ready serverless applications on AWS.
- Official
AWS Lambda Microvms
awslabs/agent-plugins
Build, run, debug, and operate applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments that run inside a container with up to 8-hour lifetimes.
- Official
AWS Lambda Durable Functions
awslabs/agent-plugins
Build resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions.
More from aws/agent-toolkit-for-aws
All 138 skills in this repo- Official
Agent Advisor
aws/agent-toolkit-for-aws
Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.
- Official
Agents Build
aws/agent-toolkit-for-aws
A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.
- Official
Launch With AWS
aws/agent-toolkit-for-aws
Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.
- Official
Processing S3 Uploads With Step Functions
aws/agent-toolkit-for-aws
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.
- Official
AWS Marketplace Metering
aws/agent-toolkit-for-aws
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…
- Official
Agents Pay
aws/agent-toolkit-for-aws
A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.
Related
Works with
Categories
Questions about Debugging Lambda Timeouts
What does Debugging Lambda Timeouts do?
Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream…. Debugging Lambda Timeouts is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. 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.
When should I use Debugging Lambda Timeouts?
Debugging Lambda Timeouts fits situations like: A Lambda function is timing out; approaching its timeout limit.
How do I install Debugging Lambda Timeouts in Claude Code?
Run `npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a claude-code`. Or copy the skill folder (skills/specialized-skills/serverless-skills/debugging-lambda-timeouts in aws/agent-toolkit-for-aws) into .claude/skills/debugging-lambda-timeouts in your project. Claude Code loads it when a task matches its description.
How do I install Debugging Lambda Timeouts in Codex?
Run `npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a codex`. Or copy the skill folder (skills/specialized-skills/serverless-skills/debugging-lambda-timeouts in aws/agent-toolkit-for-aws) into .agents/skills/debugging-lambda-timeouts in your project. Codex loads it when a task matches its description.
Can I use Debugging Lambda Timeouts in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-lambda-timeouts, .gemini/skills/debugging-lambda-timeouts, .github/skills/debugging-lambda-timeouts and .opencode/skills/debugging-lambda-timeouts in your project.
What does Debugging Lambda Timeouts need to run?
Going by SKILL.md and its folder, Debugging Lambda Timeouts needs the command-line tools its instructions call (aws).
Does Debugging Lambda Timeouts access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debugging Lambda Timeouts safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Debugging Lambda Timeouts use?
Debugging Lambda Timeouts is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debugging Lambda Timeouts use?
About 502 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.
What are the alternatives to Debugging Lambda Timeouts?
Skills that share tags, products or a category with Debugging Lambda Timeouts: CRM Production Investigation Guidelines (aws/tools-for-devops-agent, 100 stars), AWS Sam Bootstrap (giuseppe-trisciuoglio/developer-kit, 355 stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars) and AWS Serverless (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debugging Lambda Timeouts?
aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,825 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 7, 2026.
Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.