Sales Contract Audit From Seller Perspective

Problem

Sales contract review often mixes clause extraction with position judgment. The same contract can be framed as buyer-friendly or seller-risky, while converted numbers, tracked changes, and split payment milestones create inconsistent conclusions. This skill makes the seller perspective explicit and focuses on terms that disadvantage the seller, such as excessive obligations, missing protections, payment obstacles, unfavorable jurisdiction, and unilateral rights.

How It Works

The workflow standardizes text extraction, applies a priority-based review, and emits a self-contained HTML report. It uses references/extract_contract.py to extract .docx, .pdf, .txt, and .md content, filters Track Changes, normalizes whitespace, zero-width characters, and quotation marks, and outputs a SHA256 hash for consistency checks. It then loads references/audit_points.md and reviews the contract across legality, enforceability, risk controllability, and commercial alignment, with emphasis on liability clauses, invoice breach terms, unilateral termination, payment-to-invoice amount consistency, seller identification, and consolidated payment milestones. The fixed CSS and DOM structure produce sections for key terms, risk points, revision suggestions, reference clauses, and conclusion, making the output easier to reuse in engineering, legal support, or commercial review workflows.

Boundaries

The skill expects searchable text and does not support encrypted files, OCR scans, or documents with tracked changes. Amounts, ratios, and penalty figures should be quoted from the original contract rather than converted or abbreviated. It supports contract review and risk flagging, but it is not legal advice; material risks should be assessed in the business context with professional counsel.