Business Agreement Generator

Overview

Generates professional business agreements for 10 common relationship types, each with type-specific clause sections, plain English annotations, and proper legal structure. Templates are benchmarked against CommonPaper standards (CC BY 4.0), Bonterms (CC BY 4.0), and Open-Agreements (MIT) to ensure market-standard language.

The skill uses an information-gathering wizard approach — collecting essential details before generating, rather than producing generic boilerplate that requires heavy editing.

> Legal Disclaimer: This skill generates template documents for informational and > educational purposes only. Generated agreements are not a substitute for legal advice. > Contract requirements vary by jurisdiction, industry, and transaction specifics. > All documents should be reviewed by a licensed attorney before execution. No > attorney-client relationship is created by using this tool.

Prerequisites

• Names and details of all parties to the agreement
• Clear understanding of the business relationship and obligations
• Desired term, payment structure, and governing jurisdiction

Instructions

1. Identify the agreement type. Determine which of the 10 types the user needs:

1. Run the information-gathering wizard. Collect these details from the user:

Universal fields (all types):

• Full legal names and entity types of al…

Regulatory Compliance Audit

Overview

Executes a two-phase compliance analysis — detection scan followed by framework-by-framework evaluation — across 7 regulatory frameworks. Produces a compliance scorecard with letter grades (A-F) per framework, identifies specific gaps, and generates a prioritized remediation roadmap with effort estimates and timelines.

This skill reads and analyzes existing assets. It does not generate legal documents or modify any files. The output is an audit report documenting findings and recommendations.

> Legal Disclaimer: This skill generates AI-assisted compliance analysis for > informational purposes only. It does not constitute legal advice, certification, or > attestation of compliance. Regulatory requirements are complex and jurisdiction-specific. > All findings should be reviewed by qualified legal counsel and/or certified compliance > professionals. No attorney-client relationship is created by using this tool.

Prerequisites

• A live website URL or local codebase to analyze
• Access to any existing privacy policy, terms of service, or compliance documentation
• Knowledge of the business type, target audience, and geographic reach

Instructions

Phase 1: Detection Scan

1. Scan the website. Use WebFetch on the target URL to collect:

• HTML source (meta tags, structured data, accessibility attributes)
• Cookie and tracking behavior (Set-Cookie headers, JavaScript trackers)
• Form elements (input types, required fields, consent checkboxes)
• Payment indicators (payment form fields, processor scripts)
• Third-party scripts and embeds (analytics, advertising, social)
• SSL/TLS certificate presence
• Content targeting indicators (age-related content, children's themes)

1. Scan the codebase (if available). Use Glob and Grep to find:

• Privacy policy and terms of service files
• Cookie consent implementation code
• Authentication and access control patterns
• Data encryption at rest and in transit
• Logging and audit trail implementations
• Age verification or gate mechanisms
• Email sending code and unsubscribe handling
• Payment processing integrations
• Accessibility attributes (aria-*, alt text, semantic HTML)

1. Build the detection inventory. Create a structured map of findings:

Contract Compare — Version Comparison and Favorability Analysis

Side-by-side contract comparison skill that identifies every change between two versions, classifies each change by type and severity, and determines which party each modification favors. Essential during negotiation rounds when a counterparty returns a revised draft.

Overview

When a counterparty returns a revised contract, the changes they made — and the changes they quietly did not make — tell a story about their priorities and strategy. This skill performs a structured comparison that surfaces not just what changed, but the strategic significance of each change.

It detects three dangerous patterns that manual review frequently misses: indemnification drift (gradual shifting of liability across revisions), IP scope creep (expanding intellectual property assignment through small wording tweaks), and definition manipulation (redefining key terms to alter clause meaning without touching the clauses themselves).

Prerequisites

• Two versions of the same contract must be provided, either as:
• Two file paths (e.g., contract-v1.pdf and contract-v2.pdf)
• One file path and one pasted text block
• Two pasted text blocks labeled "Version A" and "Version B"
• The user should specify which version is the original (baseline) and which is the revision. If not specified, assume the first provided is the original.

Instructions

1. Ingest both versions. Read each document in full. If file paths are provided, use the Read tool.

1. Establish the structural map. Create a section-by-section outline of both documents. Note any structural changes (sections added, removed, renumbered, or reordered).

1. Perform clause-level comparison. For each section, classify changes into:

1. Analyze favorability. For each non-trivial change, determine:

• Who it favors: Party A, Party B, Neutral, or Unclear
• Severity: Minor (cosmetic/clarification), Moderate (shifts rights or obligations), Major (materially alters risk or liability)
• S…

Contract Review — Multi-Agent Orchestrator

Flagship contract review skill that spawns five parallel analysis agents, then aggregates their findings into a single executive report with a Contract Safety Score. Designed for founders, freelancers, and small-business operators who need to understand what they are signing without retaining outside counsel for every agreement.

Overview

Most contracts arrive as walls of dense legalese. A single-pass review misses nuance. This skill mirrors how a law firm reviews contracts: multiple specialists work in parallel, each with a different lens, then a senior partner synthesizes everything into a recommendation.

The orchestrator:

1. Ingests the contract (file path or pasted text).
2. Classifies the contract type and extracts metadata.
3. Launches five parallel agents (risk, plain-English, missing protections, compliance, and party-balance analysis).
4. Aggregates results into a unified report with a 0-100 Contract Safety Score.

Prerequisites

• The contract must be provided as a file path to a readable document (PDF, DOCX, TXT, MD) or pasted directly into the conversation.
• For file-based input the file must exist and be accessible via the Read tool.
• No external APIs or network access are required.

Instructions

1. Ingest the contract.

• If a file path is provided, read the full document with the Read tool.
• If the text is pasted, capture it verbatim.
• Confirm the document length; warn if it exceeds 50 pages.

1. Classify the contract. Determine the contract type from one of the following categories:

• Employment Agreement
• Independent Contractor / Freelance Agreement
• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Software License / SaaS Agreement
• Terms of Service / Terms of Use
• Privacy Policy / Data Processing Agreement
• Partnership / Joint Venture Agreement
• Lease / Real Estate Agreement
• Other (describe)

1. Extract metadata. Capture: parties, effective date, term/duration, governing law, dispute resolution mechanism, total contract value (if stated).

1. Launch five parallel agents using the Task tool. Each agent receives the full contract text and returns structured findings.

Freelancer Review — Independent Contractor Contract Analysis

Specialized contract review that evaluates agreements through 14 freelancer- specific lenses, flags worker misclassification risk using IRS criteria, and scores the contract on a Freelancer Fairness Score. Built for the 73+ million Americans who freelance and routinely sign contracts drafted by the hiring party's attorneys.

Overview

Freelancer contracts are almost always drafted by the client. This creates a structural power imbalance: the contract protects the client's interests by default, and freelancers — who typically cannot afford legal counsel for every engagement — sign terms they do not fully understand.

This skill flips the perspective. It reads the contract as if the freelancer's attorney were reviewing it, specifically looking for the patterns that most commonly harm independent workers: misclassification traps, overbroad IP assignments, missing payment protections, punitive non-competes, and scope creep enablers.

It also checks for worker misclassification risk — whether the contract's terms suggest the relationship is actually employment disguised as contracting, which creates tax and legal liability for both parties.

Prerequisites

• A contract or engagement agreement must be provided as a file path or pasted text.
• The user is assumed to be the freelancer/contractor unless stated otherwise.
• Helpful context (if available): the freelancer's industry, typical rate, and whether they have other active clients.

Instructions

1. Read the full contract. Use the Read tool if a file path is provided.

1. Evaluate through 14 freelancer lenses. Score each lens 1-10 (1 = high risk to freelancer, 10 = well-protected):

Missing Protections — Contract Gap Finder

Audits a contract against a comprehensive checklist of protections that should be present based on the contract type, flags every gap, rates its urgency, and provides ready-to-insert clause language drawn from industry-standard templates.

Overview

What a contract does not say is often more dangerous than what it does. Silence on key protections means the default rules of the governing jurisdiction apply — and those defaults rarely favor the weaker party.

This skill checks the contract against 15 universal protections that every agreement should contain, plus type-specific protections tailored to the contract category. For each missing protection, it explains the risk of omission and provides suggested clause language based on CommonPaper open-source templates (CC BY 4.0) and widely accepted market standards.

Prerequisites

• A contract must be provided as a file path or pasted text.
• The user should specify which party they represent. If not specified, the analysis defaults to the party that did not draft the contract.

Instructions

1. Read the full contract. Use the Read tool if a file path is provided.

1. Classify the contract type to select the appropriate checklist:

• Employment Agreement
• Independent Contractor / Freelance Agreement
• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Software License / SaaS Agreement
• Terms of Service / Terms of Use
• Partnership / Joint Venture Agreement
• Other (apply universal checklist only)

1. Check the 15 universal protections. Every contract should address:

NDA Generator

Overview

Generates professional non-disclosure agreements tailored to the specific relationship, jurisdiction, and scope of confidential information. Produces four NDA variants — mutual, one-way, employee, and vendor — each with 15 mandatory sections, plain English annotations, and jurisdiction-specific clauses. Templates are benchmarked against SCORE NDA patterns (SBA-funded) and CommonPaper NDA standards (CC BY 4.0).

Every generated section includes a > **Plain English:** annotation block so non-lawyers can understand the agreement without legal counsel.

> Legal Disclaimer: This skill generates template documents for informational and > educational purposes only. Generated NDAs are not a substitute for legal advice. > All agreements should be reviewed by a licensed attorney before execution. Terms > may need modification based on jurisdiction-specific requirements. No attorney-client > relationship is created by using this tool.

Prerequisites

• Names and addresses of all parties
• Clear understanding of what information is being protected
• Desired duration of confidentiality obligations
• Governing law jurisdiction (state/country)

Instructions

1. Determine NDA variant. Ask the user which type is needed:

• Mutual NDA — Both parties share confidential information (partnerships, M&A discussions)
• One-Way NDA — Only one party discloses (pitching to investors, sharing trade secrets)
• Employee NDA — Employee access to company confidential information
• Vendor NDA — Third-party vendor/contractor access to business data

1. Gather party information. Collect from the user:

• Full legal names of all parties
• Entity types (individual, LLC, Corp, etc.)
• Addresses (for notice provisions)
• State of incorporation / governing jurisdiction
• Effective date

1. Define the scope of confidential information. Determine:

• Categories of protected information (technical, financial, customer, strategic)
• Specific exclusions the user wants (publicly known information, independently developed)
• Whether oral disclosures are included (with written confirmation requirement)
• Any carve-outs for specific data types

1. Set duration and terms. Establish:

• Term of the agreement (how long parties will share information)
• Survival period (how long confidentiality obligations last after termination)
• Typical ranges: 1-3 years for term, 2-5 years for survival
• Employee NDAs: often indefinite for trade secrets

1. Genera…

Contract Negotiation Strategy Generator

Overview

Reads a contract or agreement, identifies clauses that are unfavorable, one-sided, or carry hidden risk, and produces a structured negotiation strategy document with specific counter-proposals ranked by priority. Benchmarks replacement language against CommonPaper standard clauses (CC BY 4.0) to ensure proposed alternatives reflect market norms.

This skill performs analysis only — it does not create new contracts. It reads the source document and outputs a negotiation strategy in Markdown.

> Legal Disclaimer: This skill generates AI-assisted analysis for informational > purposes only. It does not constitute legal advice. All counter-proposals and > replacement language must be reviewed by a licensed attorney before use in any > binding agreement. No attorney-client relationship is created by using this tool.

Prerequisites

• A contract or agreement file accessible in the workspace (.md, .txt, or .pdf)
• Knowledge of the user's negotiating position (buyer, seller, service provider, etc.)
• Understanding of which party the user represents

Instructions

1. Identify the contract. Locate the contract file using Glob. If multiple contracts exist, ask the user to confirm which one to analyze.

1. Read the full contract. Use Read to ingest the entire document. Note the parties, effective date, governing law, and contract type.

1. Classify the user's position. Determine which party the user represents and their leverage context (e.g., small vendor vs. enterprise buyer).

1. Scan for unfavorable clauses. Evaluate every section against these risk categories:

• Liability & Indemnification — unlimited liability, one-sided indemnity, no caps
• Termination — termination for convenience without notice, auto-renewal traps
• IP & Ownership — broad IP assignment, work-for-hire overreach
• Payment — late payment penalties without reciprocal terms, NET-90+
• Confidentiality — perpetual obligations, overly broad definitions
• Non-Compete / Non-Solicit — excessive scope, duration, or geography
• Limitation of Liability — exclusion of consequential damages only for one party
• Governing Law & Dispute — inconvenient jurisdiction, mandatory arbitration
• Data & Privacy — broad data usage rights, no breach notification
• Force Majeure — missing or one-sided

1. Prioritize findings into three tiers:

• MUST…

Plain English — Legalese to Plain Language Translator

Translates every material clause in a contract into clear, jargon-free language that a non-lawyer can understand, while flagging clauses that appear to be deliberately confusing or that hide significant obligations behind complex wording.

Overview

Legal language exists for precision, but it is also routinely weaponized. Dense legalese discourages the other party from reading carefully, hides unfavorable terms behind jargon, and creates information asymmetry that favors the drafter.

This skill neutralizes that advantage by producing a clause-by-clause translation at an 8th-grade reading level (Flesch-Kincaid grade 8 or below), accompanied by flags that highlight where the original language is not just complex but strategically confusing.

The goal is not to replace legal review but to ensure the signer actually understands what they are agreeing to before deciding whether to consult an attorney.

Prerequisites

• A contract must be provided as a file path or pasted text.
• No special knowledge from the user is required — the entire point of this skill is to make the contract accessible to anyone.

Instructions

1. Read the full contract. Use the Read tool if a file path is provided.

1. Identify all material clauses. Break the contract into individual sections and clauses. Skip boilerplate headers, signature blocks, and formatting-only content.

1. Translate each clause to plain English. For every material clause:

• Rewrite in short, direct sentences (target: 8th-grade reading level).
• Replace legal jargon with everyday equivalents:
• "indemnify and hold harmless" -> "pay for any losses and protect from lawsuits"
• "notwithstanding anything to the contrary" -> "even if other parts of this contract say differently"
• "shall not be construed to" -> "does not mean"
• "in the event of" -> "if"
• "prior to" -> "before"
• "pursuant to" -> "under" or "according to"
• "herein", "hereof", "hereunder" -> "in this contract"
• "mutatis mutandis" -> "with the necessary changes"
• Preserve the legal meaning — do not simplify away obligations or rights.
• State who must do what, by when, and what happens if they do not.

1. Apply the 5 flag types. After translating each clause, check whether any of these flags apply:

Privacy Policy Generator

Overview

Scans a website or application codebase to detect data collection signals — cookies, web forms, payment processors, analytics scripts, social media embeds, and third-party trackers — then generates a tailored privacy policy with 12 sections. Includes specific GDPR rights (7 individual rights), CCPA rights (6 consumer rights), and cookie consent banner text in both minimal and full GDPR formats.

The detection phase maps every data touchpoint to its legal basis and disclosure requirement, ensuring the generated policy accurately reflects actual data practices rather than relying on generic boilerplate.

> Legal Disclaimer: This skill generates template documents for informational and > educational purposes only. Generated privacy policies are not a substitute for legal > advice. Data protection requirements vary by jurisdiction, industry, and data type. > All documents should be reviewed by a licensed attorney and/or data protection officer > before publication. No attorney-client relationship is created by using this tool.

Prerequisites

• A live website URL or local codebase to scan
• Knowledge of the business entity name and jurisdiction
• Understanding of what data is collected and why (the scan detects signals but cannot capture server-side-only processing)

Instructions

1. Scan for data collection signals. Use WebFetch on the target URL to detect:

1. If scanning a codebase instead, use Glob and Grep to find:

• Cookie-setting code (document.cookie, setCookie, cookies middleware)
• Analytics initialization (gtag, analytics.track, mixpanel.init)
• Form handlers and data submission endpoints
• Payment SDK imports and configurations
• User model/schema definitions showing stored fields
• Environment variables referencing third-party API keys

…

Risk Analysis — Clause-by-Clause Risk Scoring

Standalone deep-dive skill that scores every material clause in a contract against ten risk categories, flags poison pills, and estimates financial exposure. Designed to surface the clauses that could cost the most money or create the most liability.

Overview

Every contract contains trade-offs. This skill systematically identifies which trade-offs are reasonable and which are dangerous by scoring clauses on a 1-10 severity scale across ten categories. It specifically hunts for "poison pills" — clauses that appear innocuous but create disproportionate risk when triggered.

Unlike a general review, this skill produces a quantified risk profile: a heat map of where the danger lives, what it could cost, and what to do about it.

Prerequisites

• A contract must be provided as a file path or pasted text.
• The user should ideally specify which party's perspective to analyze from (e.g., "I am the service provider" or "I am the client"). If not specified, the analysis defaults to the party that did not draft the contract.

Instructions

1. Read the full contract. Use the Read tool if a file path is provided.

1. Identify all material clauses. Extract each numbered section or clause that creates obligations, rights, restrictions, or liabilities.

1. Score each clause across 10 risk categories (1 = minimal risk, 10 = extreme risk):

Terms of Service Generator

Overview

Scans a website or application to understand the business model, user interactions, data collection practices, and third-party integrations, then generates a comprehensive terms of service document with 16 sections. Includes GDPR and CCPA compliance provisions, plain English summaries after each section, and [VERIFY] tags for assumptions that require human confirmation.

The generated ToS adapts its language and provisions based on the detected business type (e-commerce, SaaS, marketplace, content platform, mobile app, etc.).

> Legal Disclaimer: This skill generates template documents for informational and > educational purposes only. Generated terms of service are not a substitute for legal > advice. All documents should be reviewed by a licensed attorney before publication. > Regulatory requirements vary by jurisdiction and business type. No attorney-client > relationship is created by using this tool.

Prerequisites

• A live website URL or local codebase to analyze
• Knowledge of the business entity name and jurisdiction
• Understanding of whether the service involves payments, user accounts, or user-generated content

Instructions

1. Analyze the website or application. Use WebFetch to scan the target URL. Identify:

• Business type (SaaS, e-commerce, marketplace, content, API, mobile app)
• User interaction patterns (accounts, purchases, subscriptions, content uploads)
• Data collection mechanisms (forms, cookies, analytics scripts, payment processors)
• Third-party integrations (Stripe, Google Analytics, social login, CDNs)
• Geographic indicators (language, currency, server location)

1. If a codebase is available instead, use Glob and Read to scan for:

• Cookie/tracking implementations
• Authentication flows
• Payment integrations
• User data models
• API endpoints that accept user input

1. Gather business details from the user:

• Legal entity name and type (LLC, Corp, sole proprietor)
• Business address and jurisdiction
• Contact email for legal notices
• Minimum user age requirement
• Whether the service is free, paid, or freemium

1. Determine applicable compliance frameworks:

• GDPR — if serving EU/EEA users (detected via language, .eu domain, Euro pricing)
• CCPA/CPRA — if serving California users or meeting revenue/data thresholds
• COPPA — if the service could attract users under 13
• ADA/WCAG — if a US-based public-facing service
• PCI-DSS — if processing payment card data
…