Amazon Web ServicesCloud platform, $128.7B 2025 revenue1,600 installs on skills.shInvestigating Incidents with AWS Devops Agent
Run a deep root-cause investigation on the AWS DevOps Agent.
Use Edge to load the skill investigating-incidents-with-aws-devops-agent from aws/agent-toolkit-for-aws for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
What it does
- Run a deep root-cause investigation on the AWS DevOps Agent.
- Use when the user describes an incident, alarm, outage, or unexplained behavior : keywords like "5xx", "503", "OOM", "latency spike", "deployment failure", "rollback", "sev1", "investigate", "root cause", "debug", "alarm fired", "service down".
- Polls and streams progress, then surfaces recommendations.
Why Amazon Web Services
Amazon's cloud computing business. Each fact links its public source.
- 2025 revenue
AWS revenue was US$128.7 billion in 2025.
Wikipedia: AWS - AWS command line tool
The aws-cli repo has 17k+ GitHub stars.
GitHub repo - Cloud Development Kit
The aws-cdk repo has 12k+ GitHub stars.
GitHub repo
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Investigating Incidents with AWS Devops Agent.
Related skills
Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analy
Systematically trace bugs backward through call stack to find original trigger
4-phase root cause debugging: understand bugs before fixing.
Diagnose why a SigNoz alert fired by correlating the alert's own signal with neighbor signals (error rate, latency, throughput, CPU/memory), traces, and logs around the fire window, and rank likely causes. Make sure to u
DevOps and IT Ops automation - CI/CD, monitoring, incident management, and infrastructure workflows
Use when writing a postmortem, incident report, or root-cause analysis after an outage, a defect that reached users, a data issue, or a near miss - or when turning an incident channel, alert log, or war-room thread into
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-19: reviewed. Static scans check the code, not how well the skill works.
State definitionsSelect the Files tab to load SKILL.md.
Skill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-19: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-19
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-19
Creator, source & licenceaws
From the aws public repository. Edge did not write or edit this skill.
- Repository
- aws/agent-toolkit-for-aws
- Skill file
- View source at revision
- Revision
- e9136649bd6fee5163f81299dfd37de0dd336b18
- Package hash
- sha256:a6742837741bbc208401f1e1eebdeb62133f55561d0a7528e02a27de4873784c
- Licence
- Apache-2.0
- Description
- Run a deep root-cause investigation on the AWS DevOps Agent. Use when the user describes an incident, alarm, outage, or unexplained behavior : keywords like "5xx", "503", "OOM", "latency spike", "deployment failure", "rollback", "sev1", "investigate", "root cause", "debug", "alarm fired", "service down". Polls and streams progress, then surfaces recommendations.
Quoted from the skill’s own description
Read skill files2 files
2 files, 9.2 KB at revision e9136649bd6f.
Questions about Investigating Incidents with AWS Devops Agent
What does Investigating Incidents with AWS Devops Agent do?
Run a deep root-cause investigation on the AWS DevOps Agent. Published by Amazon Web Services (aws/agent-toolkit-for-aws).
Is Investigating Incidents with AWS Devops Agent safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 19, 2026). The Evidence tab shows the scan.
How do I use Investigating Incidents with AWS Devops Agent in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.
Similar skills

Build and troubleshoot Azure AI Search, Speech, OpenAI, and Document Intelligence apps. WHEN: AI Search, query search, vector search, hybrid…

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up…

This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to…

Deploys and configures classic Firebase Hosting for static websites, single-page apps (SPAs), and microservices. Use when deploying static s…
Deploy a self-hosted funnel builder, take a funnel from empty install to published - landing page, checkout, one-click upsell, thank-you - a…

Deploy and operate apps on Prisma Compute with the Prisma 8 CLI. Use whenever the user mentions Prisma Compute, deploying or hosting a Prism…

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link…