msp-legal

Reviews, drafts, and triages MSP contracts using a document stack and clause playbook.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running an MSP means constantly handling contracts: MSAs, Service Orders, SOWs, NDAs, DPAs, and waivers. Without a consistent playbook, every review starts from scratch, clause positions drift between deals, and risky terms slip through. This skill gives an MSP a single source of truth for its legal document stack, standing positions on contested clauses, and clear attorney-escalation rules. ## Core Features & Use Cases - Document stack map: Defines what each legal document (MSA, Service Order, SOW, SLA, NDA, DPA, BAA, waivers, Change Orders) is for, how they fit together, and which one a given client situation requires. - Negotiation playbook: Provides standard positions, acceptable ranges, and escalation triggers per clause (liability caps, indemnification, non-solicits, insurance, claim periods), formatted for use with generic contract-review skills. - Inbound contract triage: Flips the lens when reviewing paper sent by clients or vendors, hunting for the same aggressive clauses the MSP uses itself. - Use Case: A client sends back a redlined Service Order demanding a lower liability cap and termination for convenience. Load this skill to check both requests against the playbook positions, identify which changes fall inside the acceptable range, and flag the rest for attorney review. ## Quick Start Ask Claude to review this client contract against our MSP legal playbook and flag anything that needs attorney escalation.

Frequently Asked Questions about msp-legal

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

FAQPage Schema
How do I review an MSP client contract against a playbook?

Load the playbook-positions reference file, then run a clause-by-clause review comparing each term against the standard position, acceptable range, and escalation trigger. Findings get classified as errors, contradictions, enforceability questions, pricing conflicts, or small-client friction.

What legal documents does a managed service provider need?

Every client signs an MSA once as the umbrella agreement. Managed services add a Service Order carrying term, pricing, and SLA targets; projects add a SOW. Regulated-data clients need a DPA, healthcare clients need a BAA, and declined recommendations get documented with risk acceptance waivers.

Should an MSA include pricing and term commitments?

No. The MSA is the umbrella agreement and carries no term, pricing, or client-specific scope. Commercial specifics like the minimum term, discount ladder, and SLA targets live in the Service Order or SOW underneath it, keeping one MSA valid for all engagement types.

When should contract changes go to an attorney?

Escalate any client redline touching the liability cap, demands to delete the ransomware cost-allocation clause, changes to indemnification, or the non-solicit liquidated-damages figure. The skill treats these as attorney-only items and flags them rather than negotiating them directly.

Does this skill provide legal advice?

No. It provides working analysis and a negotiation playbook built from one MSP's example positions, with a standing disclaimer that load-bearing outputs require review by a licensed attorney before reliance. Shipped templates are example defaults pending attorney approval.