Contracts legal-AI skills in General

285 legal AI skills for contracts in General.

Compliance Check (Pre-Launch)

MITGeneralContracts

Pre-launch regulatory go/no-go on a PROPOSED action, product feature, marketing campaign, partnership, sub-processor addition, AI capability, geographic expansion, or pricing/auto-renewal change — BEFORE it ships. Surfaces applicable regulations across jurisdictions (GDPR, CCPA/CPRA, state privacy laws, HIPAA, COPPA, PCI-DSS, CAN-SPAM, TCPA, FTC, EU AI Act, Puerto Rico Ley Núm. 111-2005 / DACO consumer rules, sector laws), required internal approvals (legal, DPO, security, exec), required external notifications (customer DPA notice, 30-day sub-processor notice, regulator filings, insurance), required pre-launch artifacts (DPIA, updated privacy policy, consent flow, SCCs), and risk areas. Outputs a clear GO / NO-GO / GO-WITH-CONDITIONS decision with specific verifiable conditions and a re-check trigger. Use whenever the user says "is this compliant", "can we launch X", "what regulations apply to [feature/campaign/partnership/sub-processor/AI capability]", "do we need approval before [action]", "pre-launch legal/regulatory check", "go/no-go on [proposed initiative]", "are we OK to ship [thing] in [jurisdiction]", or describes wanting a forward-looking compliance view on a not-yet-shipped initiative. Do NOT use for: auditing already-published customer-facing legal pages on a live site (use legal:legal-audit), reviewing a contract document like MSA/NDA/DPA (use legal:review-contract), tracking ongoing compliance program operations like SOC 2 evidence collection or audit calendar (use operations:compliance-tracking), SOX 404 internal financial-control testing (use finance:sox-testing or finance:audit-support), responding to an inbound legal inquiry like a DSAR or subpoena (use legal:legal-response), drafting an actual outbound breach notification AFTER an incident (escalate to counsel + use legal:legal-response template path; this skill is PRE-LAUNCH design check, not post-incident response). Defining characteristic: PRE-launch + proposed thing + forward-looking go/no-go