msp-ops-kit

Use this skill whenever generating ANY document, marketing material, email, proposal, slide deck, or other customer- or internal-facing content for your MSP, so that naming, visual style, and voice stay consistent. Triggers include any request to create, write, design, or format content "for us", "for my MSP", "on brand", "branded", or anything that will carry the company's name, logo, colors, or voice: flyers, one-pagers, case studies, cold emails, sales scripts, proposals, decks, social posts, letterhead, email signatures, or web copy (content and voice only; site build and hosting is msp-website-setup). Always load this skill before producing branded output, and apply it alongside content skills like msp-sales, msp-marketing, msp-pricing, docx, and pptx.

Use this skill whenever writing an operational message to an existing client of your MSP: outage or incident notices and updates, planned or emergency maintenance announcements, post-incident summaries, security advisories ("warn our clients about this phishing wave"), price change letters, new-user-ready or user-offboarded confirmations, and ticket closing notices. Trigger on "draft an email to the client about", "let them know", "notify clients", "tell the client", or any in-service client notification. Sales outreach to prospects belongs to msp-sales; this skill owns messages to clients already under agreement. Apply alongside msp-brand (voice and signature), msp-helpdesk (priorities set the cadence), msp-legal (anything touching breach, liability, or contract mechanics), and msp-pricing (any number).

Use this skill for anything about how your MSP runs day-to-day support: setting or questioning a ticket's priority, response and resolution targets, "the client says everything is down", escalation, after-hours or emergency requests, security incident intake, triage order, your PSA (ticketing) system workflow, time entries, or ticket categories. Also trigger when drafting anything that describes support levels or response times to a client, and when training new hires on the service desk workflow (client onboarding is msp-onboarding). Apply alongside msp-client-comms (the messages clients receive during incidents), msp-legal (the SLA schedule lives in each client's Order; security incidents have contract implications), msp-pricing (after-hours billing multipliers), msp-maintenance (alerts that escalate into tickets, and the on-call rotation behind the after-hours line), and msp-metrics (ticket data feeds every business number).

Use this skill for ANY legal or contract work for your MSP: reviewing, drafting, or revising an MSA, Service Order, SOW, SLA, NDA, waiver, DPA, or BAA; triaging a contract a client or vendor sends; assessing legal risk on a deal; or answering "what document do we need for this client". Always load this skill BEFORE running any generic legal skill (legal:review-contract, legal:triage-nda, legal:legal-risk-assessment, legal:compliance-check, etc.): it is your negotiation playbook and document map, the organization-specific positions those skills ask for. Also trigger on "is this enforceable", "what should our contract say", "the client wants to change a clause", or any mention of liability caps, indemnification, non-solicits, or contract terms for an IT services business. Apply alongside msp-brand (naming and voice), msp-pricing (any term or number a client could see), and msp-sales (how legal terms land in the sales conversation).

Use this skill for your MSP's proactive, recurring operations: patching and update cycles, maintenance windows, backup monitoring and test restores, monitoring and alert triage, the on-call rotation, change management for risky changes, documentation currency, and vendor or license renewals. Trigger on "patch window", "maintenance window", "did the backups run", "test restore", "alert storm", "who is on call", "can we make this change", "update the firewall", or any question about the recurring delivery work between tickets. msp-helpdesk owns the reactive desk (tickets, priorities, response targets); this skill owns the scheduled work that prevents tickets. Apply alongside msp-client-comms (maintenance notices), msp-qbr (the scorecard rows this work feeds), msp-metrics (SLA and ticket data), msp-legal (the negligence carveout that makes these logs matter), and msp-pricing (after-hours multipliers for emergency work).