Index of every page on this site: llms.txt
All skills
aws avatar

/troubleshooting-application-failures

@12d7f78
Run it yourself

Troubleshoots failing applications by discovering and analyzing CloudWatch log groups to identify error patterns, root causes, and actionable solutions. Use when an application is experiencing failures and log-based diagnosis is needed.

Use this Skill: https://skilld.dev/gh/aws/agent-toolkit-for-aws/troubleshooting-application-failures

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈69 tokens for metadata: the name and description. ≈347 when used: this file. ≈4.3k more on demand in 1 file.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈275 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Application Failure Troubleshooting

Overview

Domain expertise for diagnosing application failures through CloudWatch log analysis. Discovers relevant log groups, searches for error patterns and stack traces, performs root cause analysis, and generates prioritized remediation recommendations.

Logs are where the investigation starts, not its boundary. When the logs point at a timeout, throttle, retry or permission problem, read the configuration that sets it, for example the API Gateway integration timeout, the queue's visibility timeout, or the function timeout and event source mapping. Read-only access normally includes these Describe and Get calls.

Troubleshoot a failing application

To diagnose and resolve application failures using CloudWatch logs, follow the procedure exactly. See Application failure troubleshooting procedure.

Troubleshooting

No log groups found

Ask the user for specific log group names. Common patterns: /aws/lambda/function-name, /aws/apigateway/api-name, or custom application log groups.

Access denied errors

Verify AWS credentials have logs:DescribeLogGroups, logs:DescribeLogStreams, logs:StartQuery, and logs:GetQueryResults permissions.

Query timeouts

Reduce the time window or limit results. Large log groups may require multiple smaller queries.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning29d3 checks · Risk SAFE
  • Gen Agent Trust Hub29d

    This skill facilitates the troubleshooting of AWS application failures by analyzing CloudWatch logs. It includes security considerations such as a potential indirect prompt injection surface due to the processing of external log data. These findings are standard for the skill's intended purpose and can be managed through appropriate agent configuration and least-privilege permissions.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: MEDIUM · 1 issue

Signed by skilld at 12d7f78. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
version
2

README badge

README badge for aws/agent-toolkit-for-aws/troubleshooting-application-failures