How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

debugging-lambda-timeouts - Skill

Name: debugging-lambda-timeouts
Author: aws

Imported from aws/agent-toolkit-for-aws (skills/specialized-skills/serverless-skills/debugging-lambda-timeouts/SKILL.md) via skills.sh. Install upstream with npx skills add aws/agent-toolkit-for-aws --skill debugging-lambda-timeouts. Copyright stays with the author.

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.

Install debugging-lambda-timeouts and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "aws-agent-toolkit-for-aws-debugging-lambda-timeouts", "kind": "skill", "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.", "publisher": "aws", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/aws/agent-toolkit-for-aws", "path": "skills/specialized-skills/serverless-skills/debugging-lambda-timeouts/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/aws/agent-toolkit-for-aws/debugging-lambda-timeouts", "key": "aws/agent-toolkit-for-aws/skills/specialized-skills/serverless-skills/debugging-lambda-timeouts/SKILL.md" } }, "instructions": "# Debugging Lambda Timeouts\n\n## Overview\n\nDomain expertise for systematically investigating AWS Lambda function timeout failures\nby analyzing function configuration, CloudWatch logs, metrics, dependencies, cold start\npatterns, and code. Identifies common causes such as insufficient timeout settings,\nexternal service delays, database connection issues, memory constraints, and inefficient\ncode patterns, then provides prioritized recommendations.\n\n## Debug a Lambda timeout\n\nTo investigate and resolve Lambda timeout issues, follow the procedure exactly.\nSee [Lambda timeout debugging procedure](ref", "cost": { "context_tokens": 404 } }

debugging-lambda-timeouts

About

Debugging Lambda Timeouts

Overview

Debug a Lambda timeout

Troubleshooting

Function not found

No logs available

Access denied errors

Log query time range issues

Use it

Install debugging-lambda-timeouts and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews