- Home
- Skills
- DevOps & Cloud
- Patch Rollout Planner
Works with the AI Agents you already use
Patch Rollout Planner
Automate safe, multi-wave patch rollouts using greedy set-cover algorithms to ensure representative pilot rings.
$1
Patch Rollout Planner
Example session with this skill installed
Plan a patch rollout for my fleet in cmdb.csv. I need a 10% pilot that covers all departments and OS versions. Use the Nov 2026 Patch Tuesday as the start date with 0, 3, 7, and 14 day delays.
- Read your context and instructions
- Compiled the patch rollout planner
- Generated the data export
I have processed your device inventory and generated a 4-ring deployment plan. The pilot ring (Ring 0) was selected using a set-cover algorithm to ensure 100% coverage of all 12 departments and 4 OS builds present in your cmdb.csv using only 9.8% of the total fleet.
Patch Rollout Plan: November 2026
| Ring | Designation | Target Date | Device Count | Selection Logic |
|---|---|---|---|---|
| Ring 0 | IT / Pilot | 2026-11-10 | 49 | Representative diversity (All Depts/OS) |
| Ring 1 | Early Adopters | 2026-11-13 | 75 | Low-criticality workstations |
| Ring 2 | Broad Deployment | 2026-11-17 | 320 | General production fleet |
| Ring 3 | Critical Systems | 2026-11-24 | 56 | Servers and high-value assets |
Deployment Schedule Details
- Base Date: 2026-11-10 (Patch Tuesday)
- Ring 0 (0d): Tuesday, Nov 10
- Ring 1 (3d): Friday, Nov 13
- Ring 2 (7d): Tuesday, Nov 17
- Ring 3 (14d): Tuesday, Nov 24
Coverage Analysis
The greedy set-cover algorithm identified that the pilot ring must include specific devices from Human Resources and Engineering that are running older 10.0.19044 builds to ensure no legacy systems are broken during the broad rollout.
Next steps
- Export the generated
rings.csvand upload it to your Intune or WSUS groups. - After the Ring 0 deadline, run the
gatecommand with your success telemetry. - Review the cluster report if the failure rate exceeds 2%.
cmdb.csv
CSV · data export
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Deployment failures often go unnoticed until a patch hits the entire fleet. This skill automates the creation of safe, representative rollout rings to catch breaking changes early.
What it does
- Smart Ring Assignment Groups devices into test, pilot, broad, and critical rings based on hardware and software diversity.
- Greedy Set-Cover Selection Ensures the pilot ring includes at least one instance of every hardware model, OS version, and department.
- Dynamic Scheduling Calculates install dates relative to Patch Tuesday or specific release dates with custom deferral offsets.
- Automated Gating Analyzes pilot results to recommend a "Promote" or "Hold" status based on failure thresholds.
- Cluster Identification Detects when failures correlate to specific device attributes like a shared application or OS build.
How it works
- Import Inventory Provide
cmdb.csvand optional software inventory files to map the environment. - Generate Rings Run the plan command to select a minimal, diverse pilot group and assign remaining devices to rollout waves.
- Calculate Schedule Set the baseline date (e.g., Microsoft Patch Tuesday) and define deferral days for each ring.
- Evaluate Results Input pilot success data to determine if the deployment is safe for the broad ring.
Frameworks & tools
This skill operates via Python scripts processing CSV data. It is compatible with Windows Update for Business, Microsoft Intune, WSUS, Configuration Manager (MECM), and Linux patch management workflows.
Why this beats prompting it yourself
Manual ring selection often misses edge-case hardware or software combinations, leading to unexpected outages. This skill uses a greedy set-cover algorithm to ensure maximum coverage with minimum pilot size, which is mathematically difficult to achieve through standard prompting.
Use cases
- Designing a 4-wave rollout for a fleet of 5,000 mixed-model Windows laptops.
- Identifying why a specific security patch failed on all devices in the Finance department.
- Scheduling monthly OS updates to avoid deployment during critical business windows.
Known limitations
Requires CSV exports with consistent headers like hostname and model. Does not integrate directly with APIs; output must be imported manually into deployment tools.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Requires CSV files with specific headers. Only supports greedy set-cover logic for pilot selection. No direct API integration for automated deployment.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago