- Home
- Skills
- DevOps & Cloud
- Maintenance Window Planner
Works with the AI Agents you already use
Maintenance Window Planner
Automate conflict-free server patching schedules with cluster anti-affinity and dependency logic.
$2.99
Maintenance Window Planner
Example session with this skill installed
Plan a 4-week patching campaign starting Oct 3rd for the attached servers. Windows are Saturdays 22:00-02:00. High capacity (6 units). Don't patch on Oct 31st. Export to ICS and CSV.
- Read your context and instructions
- Compiled the maintenance window planner
- Generated the data export
I have processed the server inventory and generated a conflict-free maintenance schedule. The plan respects all cluster anti-affinity rules, ensuring redundant pairs are never scheduled in the same window. It also sequences the database tier to finish before the application tier. A 25% safety margin was applied to all windows to account for reboot delays.
Maintenance Schedule Summary
| Window Date | Slot Time | Server Count | Total Est. Minutes | Cluster Nodes Included |
|---|---|---|---|---|
| 2026-10-03 | 22:00 - 02:00 | 5 | 180 | db-prod-01, web-01, util-01 |
| 2026-10-10 | 22:00 - 02:00 | 5 | 195 | db-prod-02, web-02, app-01 |
| 2026-10-17 | 22:00 - 02:00 | 4 | 160 | app-02, mktg-01, proxy-01 |
| 2026-10-24 | 22:00 - 02:00 | 4 | 155 | proxy-02, auth-01, mon-01 |
Note: October 31st was skipped per the blackout request.
# Execution command used:
python3 scripts/windows_plan.py servers.csv --start 2026-10-03 --window "Sat 22:00-02:00" --capacity 6 --weeks 5 --blackout 2026-10-31 --csv schedule_oct_patch.csv --ics patching_calendar.ics
Next steps
- Review
schedule_oct_patch.csvfor the full host-by-host breakdown. - Import
patching_calendar.icsinto the team's shared Outlook/Google calendar to notify stakeholders. - Validate that no new servers were added to the
db-clustersince the last inventory export.
schedule_oct_patch.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
Patching a large server fleet without triggering downtime is a high-stakes logistics problem. This skill automates the scheduling of OS upgrades and firmware maintenance while enforcing high-availability constraints. It ensures redundant nodes never go down simultaneously and dependencies are strictly followed.
What it does
- Enforce Redundancy: Prevents multiple members of the same cluster or redundancy group from being assigned to the same window.
- Manage Dependencies: Sequences patches so specific hosts, like databases, are completed before their dependent application servers.
- Calculate Capacity: Fits tasks into defined windows based on estimated duration and a configurable safety margin for reboots or rollbacks.
- Prioritize Criticality: Schedules high-priority systems earlier in the campaign to ensure stability first.
- Export Deliverables: Generates a CSV schedule for documentation and an .ics file for direct import into Outlook or Google Calendar.
How it works
- Input Inventory: Provide a CSV containing hostnames, cluster groups, criticality levels, task durations, and dependencies.
- Define Windows: Specify recurring maintenance slots, such as "Saturdays 22:00-02:00", along with blackout dates and timezones.
- Set Parameters: Define the number of weeks for the campaign and the safety margin (defaulting to 25%) to handle overruns.
- Execute Logic: Run the script to calculate the conflict-free sequence and generate the calendar files.
Frameworks & tools
This skill uses a Python-based execution engine. It interfaces with standard CSV data structures and generates RFC 5545 compliant iCalendar (.ics) files.
Why this beats prompting it yourself
Standard LLMs struggle with the multi-dimensional logic of bin-packing tasks while respecting strict temporal dependencies and anti-affinity rules. This skill uses precise logic to ensure no two cluster nodes are ever offline together, preventing accidental service outages.
Use cases
- OS Patch Campaigns: Scheduling monthly security updates across a 200-server enterprise environment.
- Firmware Upgrades: Planning rolling updates for physical hypervisors in a high-availability cluster.
- Database Migrations: Sequencing database tier maintenance before web and application tiers.
Known limitations
Requires a correctly formatted CSV input. It does not verify if the server is reachable or perform the actual patching; it is a planning and scheduling tool only.
Requires CSV input with specific columns. Does not execute patches or verify server connectivity. Logic is restricted to the provided window and capacity parameters.
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 any payment.
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