msp-maintenance

Manages recurring MSP operations including patching, backup verification, monitoring triage, on-call rotation, and change management.

75|17|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/RTFM-IT-Services-LLC/msp-claude-skills --skill msp-maintenance-rtfm-it-services-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: msp-maintenance
Source: https://github.com/RTFM-IT-Services-LLC/msp-claude-skills/tree/main/skills/msp-maintenance
Command: npx skills add https://github.com/RTFM-IT-Services-LLC/msp-claude-skills --skill msp-maintenance-rtfm-it-services-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managed service providers need consistent, documented recurring operations between tickets, but patching schedules, backup verification, alert triage, and change control often run ad hoc, creating liability exposure and missed service commitments. This skill provides a complete operational playbook for proactive maintenance work with built-in record-keeping. ## Core Features & Use Cases - Patching Cycles: Weekly automated workstation patching and monthly server maintenance windows with snapshot-first sequencing, out-of-band critical vulnerability handling, and documented exceptions. - Backup Verification: Daily backup job checks with P2 escalation for failures and monthly logged test restores per client, producing the restore log that defends against negligence claims. - Monitoring, On-Call & Change Management: Alert triage rules that eliminate noise, a weekly on-call rotation with 15-minute rollover, and a five-step change management process with rollback readiness. - Use Case: A technician preparing for the monthly server maintenance window uses this skill to confirm the snapshot-first sequence, send the planned-maintenance notice via msp-client-comms, and log the closing note that feeds the QBR scorecard. ## Quick Start Ask Claude to plan this month's server patching window using the msp-maintenance skill, including client notices and the verification checklist.

Frequently Asked Questions about msp-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule MSP server patching maintenance windows?

Schedule a monthly server maintenance window, with the shipped default being the third Thursday from 8:00 pm to midnight. Sequence each server as snapshot or verified backup first, then patches, reboot, and a per-server service verification checklist, with client notice at least 3 business days ahead.

How often should an MSP test backup restores?

Perform one hands-on test restore per client every month, rotating restore types such as file sets, mailbox items, and VM boots across the quarter. Log the date, scope, result, and technician, and treat a failed test restore as a P1-adjacent event until the chain is fixed and re-tested.

How does this skill handle after-hours alerts and on-call?

Only P1-class alerts page the on-call phone after hours; everything else waits until the next business morning. The default rotation is weekly alternating staff with a 15-minute response rollover to a secondary, and after-hours billing follows the multipliers defined in msp-pricing.

What is the difference between msp-maintenance and msp-helpdesk?

msp-helpdesk owns the reactive desk: tickets, priorities, and response targets. msp-maintenance owns the scheduled proactive work that prevents tickets, such as patching, backup verification, monitoring triage, and change management.

When should a change go through formal change management?

Any risky change such as firewall or network changes, DNS, server configuration, or tenant-wide settings requires a written plan with rollback steps, a second set of eyes, client notice when users could be affected, and a log entry in the client's documentation.