Legal-AI skills in General

1765 skills, across 35 practice areas.

SaaS legal docs (Terms of Service + Privacy Policy)

MITGeneralData protection

Use when drafting or expanding a SaaS product's Terms of Service and Privacy Policy pages — especially when a stub needs to become a full document, or when a compliance need (Twilio/A2P SMS toll-free registration, an app-store review, a data-processing request) requires real legal pages. Gives the section-by-section structure of a protective ToS and Privacy Policy, the standard protective-clause stack ('AS IS' warranty disclaimer, capped limitation of liability, indemnification, third-party-platform + AI-output disclaimers), how to research competitor structure without copying wording (copyright), the entity/governing-law/contact facts to pin down, the SMS/A2P consent language carriers require, and the JSX/marketing-page gotchas. NOT legal advice — always flag that a lawyer should review before the docs are relied on. Triggers: 'write our terms of service', 'draft a privacy policy', 'our /terms is a stub', 'legal pages for the toll-free/A2P review', 'add CCPA/GDPR section', 'terms and privacy for the app store', 'protective SaaS terms'.

SaaS License Agreement

Apache-2.0GeneralCommercial

Drafts SaaS License Agreements for cloud-based software subscriptions covering access-based licensing, fees, SLAs, IP, data protection, indemnification, and liability caps. Triggers when the user needs a SaaS agreement, software subscription contract, cloud service license, or technology subscription terms.

SaaS / Subscription Agreement Review

Apache-2.0GeneralCommercial

Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by $commercial-legal:review when a SaaS or subscription agreement is detected.

SaaS / Subscription Agreement Review

Apache-2.0GeneralCommercial

Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.

SaaS Terms of Service

MITGeneralContracts

Use when a SaaS company needs to draft terms of service governing customer access to its platform. Covers account setup, acceptable use, service levels, data ownership, subscription and billing, limitation of liability, dispute resolution, and termination. Especially relevant for MENA-facing SaaS platforms that must navigate UAE e-commerce law, DIFC/ADGM contract law, consumer protection requirements, and data protection obligations, as well as the interplay between clickwrap enforceability across civil-law and common-law jurisdictions.

SaaS Vendor Data Processing Inventory

Apache-2.0GeneralData protection

SaaS vendor data processing inventory management. Covers shadow IT discovery, API-based data flow detection, processing purpose mapping, contract status tracking, and continuous inventory reconciliation for cloud service providers.

safe

Apache-2.0GeneralCorporate

Draft and fill Y Combinator SAFE contract templates — valuation cap, discount, MFN, pro rata side letter. Standard startup fundraising documents for convertible equity. Produces signable DOCX files. Use when user says "SAFE," "simple agreement for future equity," "YC SAFE," "valuation cap," "seed round documents," or "fundraising paperwork." Includes lawyer-reviewed practice guides; see openagreements.org/editors.

SAFE — Simple Agreement for Future Equity

MITGeneralFinance

Use when drafting a SAFE (Simple Agreement for Future Equity) for a startup funding round — based on the Y Combinator post-money SAFE standard, adapted for DIFC/ADGM/Delaware, or adapted for civil-law jurisdictions (LB/FR as "promesse de souscription") or KSA (where convertible debt may be preferable). Covers key economic terms (valuation cap, discount rate, MFN), conversion mechanics (equity financing, liquidity event, dissolution), jurisdictional adaptations, and the critical distinction from convertible notes. Triggers on "SAFE", "simple agreement for future equity", "convertible instrument", "pre-seed funding", or "startup financing" requests.

Sanctions Screening

MITGeneralSanctions

Use when a compliance officer, lawyer, or KYC analyst needs to check whether a person, entity, vessel, or aircraft appears on any active sanctions list before entering a transaction, onboarding a client, or executing a payment. Runs multi-list screening in parallel: OFAC (US), UN Consolidated, EU Consolidated, UK HMT OFSI, KSA NCASGS, UAE EOCN, and Lebanon BDL-SIC. Uses fuzzy name matching with transliteration awareness, DOB, POB, and ID-number matching. Always pairs with UBO lookup — screen beneficial owners, not just direct counterparties.

Sanctions Screening Documenter

MITGeneralSanctions

Document sanctions screening of customers, counterparties, beneficial owners, controllers, vessels, aircraft, addresses, and transactions against applicable official lists and restrictions. Use for onboarding, periodic or event-driven rescreening, alert disposition, ownership-and-control review, and audit evidence.

SARFAESI Advisor

MITGeneralLitigation

Assesses and plans Indian secured-creditor enforcement under the SARFAESI Act and Security Interest Enforcement Rules. Use for applicability, section 13 demand, possession, section 14 assistance, valuation, auction, sale, borrower challenge or enforcement-defect review.

Schedule / Annex Builder

MITGeneralGeneral practice

Use when building, structuring, or populating schedules, annexes, or exhibits to be attached to any principal contract. Covers MSA/SOW, share purchase agreements, leases, employment contracts, and any other instrument where voluminous, fact-specific, or frequently-updated material belongs outside the body. Ensures correct numbering, cross-referencing, conflict-of-terms hierarchy, and amendment mechanics across MENA and common-law contexts.

Scope Change Controller

Apache-2.0GeneralGeneral practice

Scope management for legal matters — baseline capture, in-flight change control, OOS documentation, and scope retrospective. Use when asked to review scoping assumptions, assess whether work is in or out of scope, draft a scope change notice, track scope changes, prepare an OOS justification, run an OOS report, prepare a scope call agenda, or review what changed on a matter. Trigger on: 'scope change', 'out of scope', 'OOS', 'scope creep', 'is this in scope', 'the client wants us to also', 'additional work', 'scope review', 'what changed from the original scope', 'we need to revisit the quote', 'the budget assumed', 'OOS report', 'scope call with the client', 'run a scope report'.

Screening Alert Adjudication

MITGeneralRegulatory

Adjudicates whether a hit generated by sanctions, PEP, or adverse-media screening is a true positive, false positive, or requires human escalation. Use whenever a user presents a screening alert, a name match against a watchlist (OFAC SDN, EU consolidated list, UK OFSI, UN list, PEP list, adverse media hit, etc.), or asks to clear a screening hit / reduce false positives / determine whether a flagged name is actually the listed party. Use even when the user describes the task casually — "is this person actually on the sanctions list", "did we get a real match", "clear this alert", "I have a hit on X" — these are all screening-adjudication tasks. Produces a deterministic determination with full audit trail (structured JSON + human-readable narrative). Designed for use by compliance analysts and screening systems.

Screen Trademark

MITGeneralIP

Screen a proposed trademark for conflicts and distinctiveness before filing. Covers trademark database searches (TMview, WIPO Global Brand Database, USPTO TESS), distinctiveness analysis using the Abercrombie spectrum, likelihood of confusion assessment using DuPont factors and EUIPO relative grounds, common law rights evaluation, and goods/services overlap analysis. Produces a conflict report with a risk matrix. Use before adopting a new brand name, logo, or slogan — distinct from patent prior art search, which uses different databases, legal frameworks, and analysis methods.

Search Engine Erasure (Right to Be Forgotten)

Apache-2.0GeneralData protection

Implements the right to be forgotten in search engines under GDPR Article 17 and the CJEU Google Spain ruling (C-131/12). Covers delisting request procedures, criteria assessment balancing privacy against public interest, and geographic scope determination. Activate for right to be forgotten, search delisting, Google Spain, de-indexing queries.

Search Prior Art

MITGeneralIP

Search for prior art relevant to a specific invention or patent claim. Covers patent literature, non-patent literature (academic papers, products, open source), defensive publications, and standard-essential patents. Use when evaluating whether an invention is novel and non-obvious before filing, challenging the validity of an existing patent, supporting a freedom-to-operate analysis, documenting a defensive publication, or responding to a patent office action questioning novelty or obviousness.

Search Prior Art

MITGeneralIP

Search for prior art relevant to a specific invention or patent claim. Covers patent literature, non-patent literature (academic papers, products, open source), defensive publications, and standard-essential patents. Use when evaluating whether an invention is novel and non-obvious before filing, challenging the validity of an existing patent, supporting a freedom-to- operate analysis, documenting a defensive publication, or responding to a patent office action questioning novelty or obviousness.

Search Prior Art

MITGeneralIP

Prior art search for invention|patent claim. Patent + non-patent (academic, products, OSS), defensive pubs, standard-essential patents. Use → eval novelty+non-obvious pre-file, challenge existing patent validity, support FTO analysis, document defensive pub, respond to office action questioning novelty.

Secretarial Compliance Checker (India)

MITGeneralLitigation

Checks recurring and event-based secretarial, governance, register, meeting, beneficial-ownership, share-capital, accounts, audit, charge, director, key-managerial-personnel, and MCA filing obligations for an Indian company. Use when a user needs a company-law compliance calendar, filing audit, statutory-register review, missed-deadline assessment, annual compliance check, or remediation plan. Use current official Companies Act, rules, notifications, MCA forms and instructions, and applicable ICSI Secretarial Standards because forms, exemptions, thresholds, and due dates change.

Secure Data Destruction

Apache-2.0GeneralData protection

Implements NIST SP 800-88 Rev. 1 media sanitization procedures including Clear, Purge, and Destroy methods for all media types. Covers certificate of destruction generation, verification procedures, vendor management for third-party destruction, and chain of custody documentation. Activate for data destruction, media sanitization, secure erasure, certificate of destruction queries.

Securities Compliance Checker

MITGeneralLitigation

Maps current Indian securities-law approvals, eligibility, pricing, disclosures, filings and timelines for an issue or transaction. Use for public, rights, preferential, private-placement, debt, takeover, buyback, listing or listed-company capital actions.

Security Agreement

MITGeneralFinance

Use when drafting a security agreement, charge, pledge, mortgage, or any instrument that grants a secured creditor rights over specific collateral to secure an underlying obligation. Covers asset-based lending, real property mortgages, share pledges, floating charges, and Sharia-compliant security structures across DIFC, ADGM, UAE onshore, KSA, LB, UK, and EU. Flags perfection requirements per jurisdiction — missing perfection renders security subordinate in insolvency.

Security Best Practices

Apache-2.0GeneralGeneral practice

Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.