Skip to content
TrustedSkillsbeta
Back to all skills

Incident Response

Official
anthropics·vlatest·devops·Apache-2.0

This skill automates incident investigation & remediation steps, rapidly reducing downtime and improving security posture by streamlining responses.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add anthropics/knowledge-work-plugins --skill incident-response -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

anthropics

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned anthropics/knowledge-work-plugins at da38ec1ee8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
da38ec1ee8
Manifest
engineering/skills/incident-response/SKILL.md
Scanned
1 file, 149 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The incident-response skill enables AI agents to autonomously detect, analyze, and remediate system outages or security breaches. It leverages real-time monitoring data to execute predefined playbooks for restoring service stability without human intervention.

When to use it

  • Automating the initial triage of server crashes detected by your observability stack.
  • Executing emergency rollback procedures when a deployment triggers critical error rates.
  • Coordinating immediate isolation of compromised network segments during active security incidents.
  • Generating structured incident reports for human stakeholders while remediation is underway.

Key capabilities

  • Real-time anomaly detection across infrastructure metrics.
  • Automated execution of containment and recovery playbooks.
  • Dynamic log aggregation and correlation for root cause analysis.
  • Status broadcasting to communication channels (e.g., Slack, PagerDuty) upon event trigger.

Example prompts

  • "Analyze current CPU and memory spikes in the production cluster and initiate the standard cooling playbook."
  • "Detect unauthorized access patterns on the API gateway and isolate the affected service instances immediately."
  • "Summarize the last 15 minutes of system logs regarding the database latency issue and propose a fix based on our runbook."

Tips & gotchas

Ensure your incident response playbooks are rigorously tested in staging environments before enabling autonomous execution, as incorrect automation can exacerbate outages. This skill relies heavily on accurate telemetry; incomplete or noisy monitoring data may lead to false positives or missed detections.