Skip to content

Patch Tuesday Response Process

Runs a repeatable monthly process to triage, test and deploy Microsoft Patch Tuesday updates by risk.

Stars
35,430
Licence
Apache-2.0
Files
7 files

What it does

This skill gives the agent a structured playbook for Microsoft's monthly security updates, which Microsoft releases on the second Tuesday of each month. It walks through the steps from reading the advisories to testing, phased rollout across deployment rings, and validation scanning, with response deadlines based on risk (for example, actively exploited flaws within 24-48 hours). It also includes two Python scripts that can pull Microsoft advisory data, cross-check the CISA known-exploited list and EPSS exploit-likelihood scores, and produce a prioritized deployment plan.

Great for

  • IT security or operations staff building or improving a monthly Windows and Office patching workflow
  • Teams using WSUS, SCCM/MECM or Intune who need a ring-based rollout plan
  • Students learning vulnerability management and patch prioritization

Skip it if

  • People who need a live patch status for their own machine: the skill describes a process and does not patch systems itself
  • Environments where the scripts would run with production credentials without review, since they call external APIs and scan targets with stored credentials

Try asking

  • “Build a monthly Patch Tuesday response process for our company's Windows servers and workstations”
  • “Help me prioritize this month's Microsoft CVEs by severity, exploitation status and EPSS score”
  • “Draft a ring-based deployment schedule for Patch Tuesday updates with rollback steps”
  • “Create a checklist for the Monday before Patch Tuesday”
Step-by-step guide: how to use Patch Tuesday Response ProcessInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 7 original files, the Apache-2.0 licence and an attribution note.

    building-patch-tuesday-response-process.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip building-patch-tuesday-response-process.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip building-patch-tuesday-response-process.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

  • Review scripts/agent.py and scripts/process.py before running them, and use a read-only or test API key first
  • Treat the SLA table as a starting template and align it with your own change-management and risk policies
  • Have the agent output the plan as a CSV or checklist for human review rather than letting it make deployment changes directly

What's inside

  • assets/template.md
  • references/api-reference.md
  • references/standards.md
  • references/workflows.md
  • scripts/agent.py
  • scripts/process.py
  • SKILL.md

Redistributed unmodified from mukul975/Anthropic-Cybersecurity-Skills under the Apache-2.0 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.