Skip to content
Get packs

AWS CloudWatch Investigation

Guides an agent through structured AWS CloudWatch incident triage with query templates and decision trees.

Source Download skill
Repository
github/awesome-copilot
Stars
40,703
Licence
MIT
Files
1 file

What it does

This skill gives an AI agent a playbook for investigating production problems on AWS. It supplies ready-made CloudWatch Logs Insights queries for spotting error spikes, slow operations, Lambda cold starts, memory exhaustion and timeouts, plus a step-by-step method for narrowing an incident from account and region down to a single resource. It also explains how to match an alarm to a recent deployment found in CloudTrail and how to express metric queries for dashboards. The agent still needs access to your AWS environment and its own tools to run these queries; the skill only supplies the method.

Great for

  • On-call engineers triaging a CloudWatch alarm on Lambda, ECS or API Gateway workloads
  • Platform teams who want a consistent incident checklist across AWS accounts
  • Engineers who want to check whether a recent CI/CD deployment caused an alarm

Skip it if

  • Non-AWS stacks or teams that do not use CloudWatch, since the queries and namespaces are AWS-specific
  • Making production changes during an incident without review, because the skill is read-oriented guidance and does not replace human judgement about rollbacks
  • Compliance-critical conclusions, since the deploy correlation rules are heuristics and can give false positives

Try asking

  • “Investigate why our payment-processor Lambda alarm fired at 14:20 and check for recent deployments”
  • “Run an error spike query across our log groups for the last hour and group by log stream”
  • “Narrow down whether this API Gateway latency spike is limited to one account, region or function”
  • “Check whether Lambda functions are running out of memory or hitting timeouts this morning”
Step-by-step guide: how to use AWS CloudWatch InvestigationInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    aws-cloudwatch-investigation.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip aws-cloudwatch-investigation.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip aws-cloudwatch-investigation.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the agent the alarm name, the approximate alarm time and the affected resource so it can fill in the placeholders in the queries
  • Review any query before running it against production logs, since broad Logs Insights scans can be slow and costly
  • Treat the deploy correlation result as a lead to verify, not a confirmed root cause

What's inside

  • SKILL.md

Redistributed unmodified from github/awesome-copilot under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.