Business Agreement Generator
Turns a short Q&A into a complete business agreement with plain-English annotations — freelancer contracts, partnerships, SOWs, MSAs and more.
Pure prompt-driven skill: no credentials, no destructive operations, no network side effects; embedded legal disclaimers and attorney-review recommendations make data flow transparent. Deducted for: unverified publisher, unknown repository license metadata, no statement on handling of sensitive legal inputs (no data-retention/privacy note), and no rollback concept.
Well-structured prompt: fixed information-gathering phase (questions 1-5 required), universal agreement template, type-specific clause inserts, deterministic file naming — happy path is plausible. Deducted for: static review cannot execute; no defined failure feedback for abnormal inputs (contradictory or invalid parameters); no tests or complete example outputs; many bracket placeholders ([15/30], [2/3/5] years) leave determinism to the user.
Clear invocation (/legal agreement <type>), ten well-bounded agreement types, clarification on unmatched types — good trigger precision. Deducted for: US-law defaults (IRS 1099, California non-compete notes, JAMS/AAA) with no declared jurisdictional boundaries; no Chinese-language support; limited fit for mainland-China users.
Well-layered docs: invocation, supported types, two-phase workflow, template plus type-specific clauses, output spec. Deducted for: unknown license, no version or changelog, no FAQ, no known-limitation disclosure (e.g., common-law/US-only applicability), unclear maintenance responsibility and update path; README is marketing-heavy (Skool community promotion) with weak governance signals.
As a drafting aid, output structure is complete (15-section standard structure + type clauses + risk-level flags) with plain-English annotations and a fill-in checklist — some marginal value. Deducted for: static review cannot verify legal quality or direct usability of generated agreements; validity is jurisdiction-dependent with no third-party evidence; README claims like '60 seconds' are unverified marketing.
All content is author claims and embedded templates: no tests, no example generated outputs, no third-party execution evidence or cross-source corroboration. Per static calibration, only the lowest tier is awarded.
- Generated agreements are not legal advice; a licensed attorney must review under the applicable jurisdiction before signing.
- Templates default to US jurisdiction (1099, California non-compete rules, JAMS/AAA); substantial rework is needed for mainland China or other jurisdictions, and there is no Chinese-language support.
- Repository license is unknown; confirm terms before commercial use.
- Many placeholders (durations, percentages, state names) require manual completion; direct use carries legal risk.
- Not execution-verified: all quality claims come from the author; this assessment is a static source review.
What does this skill do, and when should you use it?
This is one skill inside the 14-skill AI Legal Assistant collection for Claude Code, invoked via `/legal agreement <type>`. It first gathers structured details from the user (parties, scope, payment terms, duration), then drafts a full agreement with 15 standard sections, each annotated in plain English and flagged with red/yellow/green risk levels. Output is a named Markdown file plus a summary listing fill-in items and next steps. The generated document carries an explicit disclaimer that it is not legal advice and should be attorney-reviewed before signing.
Reads the /legal agreement <type> invocation and matches it against 10 supported types (freelancer-contract, partnership-agreement, service-agreement, licensing-agreement, consulting-agreement, sow, msa, joint-venture, distribution-agreement, referral-agreement). Works in phases: Phase 1 asks a numbered questionnaire (minimum questions 1-5: both parties, scope, payment, duration) plus type-specific follow-ups; Phase 2 drafts the agreement with purpose/recitals, scope, term and termination, compensation, IP, confidentiality, limitation of liability, indemnification, dispute resolution, force majeure, and signature blocks, inserting type-specific clauses (e.g., kill fee and revision limits for freelancer contracts, capital contributions and dissolution for partnerships). It saves the file as [TYPE]-AGREEMENT-[PartyA-PartyB]-[YYYY-MM-DD].md and outputs an overview, section list, [FILL IN] items, tiered risk reminders, and suggested next steps including running /legal review for risk analysis.
- A freelancer needs a contractor agreement with kill fee, revision limits, and IP assignment before starting a project
- Two small-business partners want a first-draft partnership agreement covering profit split, voting, and dissolution triggers
- A vendor under an existing MSA needs a project SOW with milestones, acceptance criteria, and a change-order process
- A software or content owner needs a licensing agreement specifying exclusivity, territory, and royalty structure
- An agency wants a referral agreement defining fee percentage, qualification criteria, and attribution windows
What are this skill's strengths and limitations?
- Covers 10 common agreement types, each with tailored follow-up questions and custom clauses
- Plain-English annotation on every section helps non-lawyers understand what they are signing
- Built-in red/yellow/green risk flags, e.g., explicit warning that non-competes are unenforceable in California, Minnesota, Oklahoma, and North Dakota
- Consistent 15-section structure including termination, confidentiality, liability caps, force majeure, and signature blocks
- Output is a template draft only; the skill itself insists on attorney review before signing
- Does not produce PDF reports — that capability belongs to a sibling skill (legal-report-pdf), not this one
- License is unknown, so commercial use terms are unverified
- No test suite or sample outputs in the source to verify draft quality; governing law and jurisdiction are left as placeholders
How do you install this skill?
Install as part of the full collection: curl -fsSL https://raw.githubusercontent.com/zubair-trabzada/ai-legal-claude/main/install.sh | bash installs all 14 skills, 5 agents, and PDF scripts. The skill file lives at skills/legal-agreement/SKILL.md in the repo. Manual steps for installing only this sub-skill are not documented in the source.
How do you use this skill?
In Claude Code, run /legal agreement <type> with a type from the supported list (e.g., /legal agreement freelancer-contract). Answer the numbered questions (at least 1-5 covering parties, scope, payment, and duration), optionally answering type-specific follow-ups. After generation, review the [FILL IN] placeholders and risk notes in the output file.