Nx Plugin For AWS
awslabs/nx-plugin-for-aws
Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators.
Troubleshoots failing applications by discovering and analyzing CloudWatch log groups to identify error patterns, root causes, and actionable solutions.
Install Troubleshooting Application Failures
$ npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-application-failures -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-application-failures --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/operations-skills/troubleshooting-application-failures .claude/skills/troubleshooting-application-failures && 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 "troubleshooting-application-failures" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/operations-skills/troubleshooting-application-failures into .claude/skills/troubleshooting-application-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-application-failures", 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/operations-skills/troubleshooting-application-failuresType 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 troubleshooting-application-failures -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-application-failures --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/operations-skills/troubleshooting-application-failures .agents/skills/troubleshooting-application-failures && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "troubleshooting-application-failures" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/operations-skills/troubleshooting-application-failures into .agents/skills/troubleshooting-application-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-application-failures", 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 troubleshooting-application-failures -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-application-failures --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/operations-skills/troubleshooting-application-failures .cursor/skills/troubleshooting-application-failures && 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 "troubleshooting-application-failures" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/operations-skills/troubleshooting-application-failures into .cursor/skills/troubleshooting-application-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-application-failures", 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/operations-skills/troubleshooting-application-failures--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 troubleshooting-application-failures -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-application-failures --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/operations-skills/troubleshooting-application-failures .gemini/skills/troubleshooting-application-failures && 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 "troubleshooting-application-failures" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/operations-skills/troubleshooting-application-failures into .gemini/skills/troubleshooting-application-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-application-failures", 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 troubleshooting-application-failuresInstalls 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 troubleshooting-application-failures -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/operations-skills/troubleshooting-application-failures .github/skills/troubleshooting-application-failures && 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 "troubleshooting-application-failures" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/operations-skills/troubleshooting-application-failures into .github/skills/troubleshooting-application-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-application-failures", 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 troubleshooting-application-failures -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 troubleshooting-application-failures --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/operations-skills/troubleshooting-application-failures .opencode/skills/troubleshooting-application-failures && 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 "troubleshooting-application-failures" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/operations-skills/troubleshooting-application-failures into .opencode/skills/troubleshooting-application-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-application-failures", 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
troubleshooting-application-failures- GitHub stars
- 2.8k
- Token cost
- ~334 tokens
- SKILL.md length
- 108 words
- Files
- 2 (incl. references)
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Troubleshoots failing applications by discovering and analyzing CloudWatch log groups to identify error patterns, root causes, and actionable solutions.
- An application is experiencing failures and log-based diagnosis is needed
- SKILL.md covers Overview, Troubleshoot a failing… and Troubleshooting
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Root cause analysis
What it does
Troubleshooting Application Failures is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. 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.
Its SKILL.md is about 330 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/application-failure-troubleshooting.md`).
It sits in Development, covering Root cause analysis. It works with Amazon Web Services and AWS Lambda. 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
- An application is experiencing failures and log-based diagnosis is needed
- Tasks that involve Root cause analysis
Example prompts
- “Use the troubleshooting-application-failures skill to troubleshoot failing applications by discovering and analyzing CloudWatch log groups to…”
- “/troubleshooting-application-failures”
What it can do on your machine
Read from SKILL.md and the folder at commit bd49cc8. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Troubleshooting Application Failures loads about 334 tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 108 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 bd49cc8, republished under its Apache-2.0 licence (© aws). 108 words, ~334 tokens.
Download SKILL.mdSave it as
.claude/skills/troubleshooting-application-failures/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- troubleshooting-application-failures
- description
- 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.
- version
- 1
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.
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.
© 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/operations-skills/troubleshooting-application-failures of aws/agent-toolkit-for-aws.
- SKILL.md
- references/application-failure-troubleshooting.md
Open the folder on GitHubat commit bd49cc8
Compare with similar skills
Troubleshooting Application Failures 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 |
|---|---|---|---|---|---|---|
| Troubleshooting Application Failures this skillaws/agent-toolkit-for-aws | 2.8k | — | ~334 | Automated safety check: Pass | Apache-2.0 | |
| Nx Plugin For AWSawslabs/nx-plugin-for-aws | 151 | — | ~3.6k | 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 | |
| New Event Sourceaws/aws-lambda-dotnet | 1.7k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| AWS Cloud Advisortech-leads-club/agent-skills | 7k | — | ~2.1k | Automated safety check: Pass | CC-BY-4.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.
- Official
New Event Source
aws/aws-lambda-dotnet
Add a new AWS event source attribute (e.g., Kinesis, Kafka, MQ) to the Lambda .NET Annotations framework, including the attribute class, source generator integration, CloudFormation writer, unit…
AWS Cloud Advisor
tech-leads-club/agent-skills
Answers AWS architecture, security and service-selection questions by searching AWS documentation through MCP tools first, then adapting advice to your stack and team.
- Official
AWS Lambda Managed Instances
awslabs/agent-plugins
Evaluate, configure, and migrate workloads to AWS Lambda Managed Instances (LMI).
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 Troubleshooting Application Failures
What does Troubleshooting Application Failures do?
Troubleshoots failing applications by discovering and analyzing CloudWatch log groups to identify error patterns, root causes, and actionable solutions. Troubleshooting Application Failures is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Troubleshoots failing applications by discovering and analyzing CloudWatch log groups to identify error patterns, root causes, and actionable solutions.
When should I use Troubleshooting Application Failures?
Troubleshooting Application Failures fits situations like: an application is experiencing failures and log-based diagnosis is needed; tasks that involve Root cause analysis.
How do I install Troubleshooting Application Failures in Claude Code?
Run `npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-application-failures -a claude-code`. Or copy the skill folder (skills/specialized-skills/operations-skills/troubleshooting-application-failures in aws/agent-toolkit-for-aws) into .claude/skills/troubleshooting-application-failures in your project. Claude Code loads it when a task matches its description.
How do I install Troubleshooting Application Failures in Codex?
Run `npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-application-failures -a codex`. Or copy the skill folder (skills/specialized-skills/operations-skills/troubleshooting-application-failures in aws/agent-toolkit-for-aws) into .agents/skills/troubleshooting-application-failures in your project. Codex loads it when a task matches its description.
Can I use Troubleshooting Application Failures 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 troubleshooting-application-failures -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/troubleshooting-application-failures, .gemini/skills/troubleshooting-application-failures, .github/skills/troubleshooting-application-failures and .opencode/skills/troubleshooting-application-failures in your project.
What does Troubleshooting Application Failures need to run?
SKILL.md names no scripts, command-line tools or credentials: Troubleshooting Application Failures is instructions for the agent only.
Does Troubleshooting Application Failures 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 Troubleshooting Application Failures 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 Troubleshooting Application Failures use?
Troubleshooting Application Failures 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 Troubleshooting Application Failures use?
About 334 tokens (SKILL.md is roughly 1.3k 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 Troubleshooting Application Failures?
Skills that share tags, products or a category with Troubleshooting Application Failures: Nx Plugin For AWS (awslabs/nx-plugin-for-aws, 151 stars), AWS Sam Bootstrap (giuseppe-trisciuoglio/developer-kit, 355 stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars) and New Event Source (aws/aws-lambda-dotnet, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Troubleshooting Application Failures?
aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,816 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.