Contract Intelligence Assistant

Problem

Contract workflows often stall on repetitive cleanup: locating contract numbers, amounts, parties, and breach clauses in PDF or DOCX files; manually checking risks against a checklist; and filling templates while preserving placeholders. This skill turns that process into an explicit agent workflow to reduce manual assembly and omissions.

How It Works

• Information extraction: parses PDF/DOCX files or pasted text, then outputs structured fields such as contract number, amount, parties, and breach clauses, with a .docx result.
• Risk review: scans risks using A/B/C levels and 16 rules, producing risk_summary, checklist, risks, and an overall assessment, then converts the report into a document.
• Template generation: identifies service, meeting platform, sales, equipment procurement, and construction procurement contracts; fills 【】 placeholders in .docx source templates and performs replacement or insertion post-processing.
• Prompt self-maintenance: parses user feedback, stores knowledge, decides whether to optimize prompts, and supports archiving and rollback.

Boundaries

It is best for existing contract text or template workflows that need structured output and document delivery. Risk conclusions depend on the rule base and prompts, and this skill does not replace legal advice. File generation also depends on local scripts and the Wiki directory, so path or dependency issues can affect output.