saas-msa-review

Reviews SaaS subscription agreements against playbook positions on renewal, pricing, data exit, and SLAs.

4|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/BoardAI/vallor-plugins --skill saas-msa-review-boardai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: saas-msa-review
Source: https://github.com/BoardAI/vallor-plugins/tree/main/vallor/skills/saas-msa-review
Command: npx skills add https://github.com/BoardAI/vallor-plugins --skill saas-msa-review-boardai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? SaaS subscription agreements carry risks that compound over time — auto-renewal lock-ins, price escalators, data lock-in, and shifting subprocessor lists — and reviewing them clause by clause against a team's legal playbook is slow and inconsistent. This Skill applies a structured SaaS-specific review overlay on top of the standard vendor agreement playbook. ## Core Features & Use Cases - SaaS-specific term analysis: Checks auto-renewal mechanics, price escalation, data portability and exit rights, uptime SLAs, subprocessors, and service deprecation against the team's configured playbook positions. - AI/ML rights and liability cap procedures: Works through a seven-dimension AI training rights analysis and a four-part liability cap breakdown (direct vs. indirect, cap base, carveouts, capped surface). - Renewal handoff: Extracts renewal dates and notice windows into a structured YAML record for the renewal-tracker skill. - Use Case: A legal team receives a counterparty's SaaS order form and MSA; the Skill produces a review memo with dual legal/business severity ratings, flags deviations from playbook positions, and records the renewal deadline for tracking. ## Quick Start Review this SaaS subscription agreement against our playbook and flag any auto-renewal, data exit, or AI training rights issues.

Frequently Asked Questions about saas-msa-review

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

FAQPage Schema
How do I review a SaaS agreement for auto-renewal risks?

Check the renewal term length, notice-to-cancel window, notice method, and price on renewal against your team's playbook positions. The Skill extracts the exact renewal date and cancel-by deadline and hands them to a renewal tracker so the window is never missed.

What should I look for in SaaS contracts regarding AI training rights?

Work through seven dimensions: explicit training grants, implicit grants via incorporated privacy policies, anonymization standards, competitive contamination, opt-out scope and durability, output ownership, and downstream regulatory exposure. Silence on all seven is itself a finding worth flagging.

Does this review work for both SaaS vendors and customers?

Yes, the Skill determines which side the company is on and loads the matching sales-side or purchasing-side playbook section. If the side is ambiguous, such as reseller or white-label deals, it asks before proceeding.

How are liability caps analyzed in SaaS agreements?

The analysis separates direct from consequential damages, quotes the cap base verbatim since definitions vary widely, enumerates carveouts sitting above the cap, and assesses whether the remaining capped surface is meaningful for the vendor's risk profile.

What happens when the playbook doesn't cover a SaaS term?

The Skill asks for the team's position on the uncovered term, records the answer into the practice-level configuration file, and then proceeds with the review. It never applies hardcoded default thresholds.

When should SLA terms not be negotiated in a SaaS deal?

Skip SLA negotiation when the service is not business-critical, such as a nice-to-have survey tool. The Skill recommends spending negotiating capital only where the business actually depends on uptime.