agents-debug

Diagnose broken AgentCore agents by analyzing traces, logs, and CLI prerequisites.

2.3k|234|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill agents-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-debug
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/plugins/aws-agents/skills/agents-debug
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill agents-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues. Reads traces and logs to diagnose root causes. Also checks prerequisites when the CLI itself isn't working. Triggers on: "agent not working", "wrong answer", "agent error", "tool call failing", "debug agent", "check logs", "read traces", "broken", "500 error", "424 error", "model access denied", "command not found", "stuck in DELETING", "maxVms exceeded", "cold start diagnosis", "cold start slow", "agentcore create error", "create failed", "exit code 7", "connection refused local dev". Not for deploy failures — use agents-deploy. Not for performance tuning without errors — use agents-optimize.

Core Features & Use Cases

  • The skill provides diagnostic steps to identify CLI/prerequisite issues and agent behavioral problems by inspecting traces, logs, and runtime configuration.
  • It guides users through verifying CLI version, reading traces/logs, and diagnosing common problems with targeted actions and references.
  • Use Case: When an agent returns incorrect results or tool calls fail, load traces and logs to determine root causes and reference doctor.md for prerequisites.

Quick Start

Describe the issue you're facing to start diagnostics and get step-by-step guidance.

Frequently Asked Questions about agents-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug an AgentCore agent that is returning wrong answers?

To debug an agent returning wrong answers, you need to analyze AgentCore traces and logs. This diagnostic process reads runtime data to identify root causes and applies targeted fixes referenced in doctor.md.

Why does my AgentCore tool call keep failing with a 500 error?

A 500 error during an AgentCore tool call indicates a runtime failure. You can diagnose the exact failure cause by loading agent traces and logs to inspect the execution path and apply the appropriate fixes from doctor.md.

What should I do if the AgentCore CLI throws a command not found error?

If the AgentCore CLI throws a command not found error, you should verify your CLI version and check system prerequisites. The diagnostic process checks these prerequisites to resolve CLI startup issues and guide installation.

How do I diagnose cold start latency issues in hosted AgentCore runtimes?

To diagnose cold start latency issues in hosted runtimes, you analyze AgentCore traces and logs. This inspection helps determine if the slow startup is caused by configuration problems or runtime constraints to apply fixes.

Can I use this diagnostic approach for AgentCore deployment failures?

No, you should not use this diagnostic approach for AgentCore deployment failures. Deployment issues require a separate workflow, while this specifically diagnoses wrong answers, tool failures, timeouts, and CLI problems.

How do I troubleshoot a stuck DELETING state or maxVms exceeded error in AgentCore?

To troubleshoot a stuck DELETING state or maxVms exceeded error, you inspect AgentCore traces and logs. Analyzing these diagnostics helps identify the runtime blockage and guides the necessary corrective actions from doctor.md.