SuperAPI AI Directory

contract-review

General & other

View repository

Updated 10-16 08:43

About this skill

Contract Review

A contract review skill for scenarios involving corporate legal, procurement, sales, operations, HR, and business owners.

The goal is not just to give general comments that "find a few risk points", but to form a review chain that can be rechecked:

  • First define the review goal and applicable standards
  • Then break down clauses and missing items
  • Then check laws and regulations and company rules
  • Then form risk classification, revision suggestions, and signing opinions

What to read first

Applicable input

  • Full contract or excerpt, pasted directly into the conversation
  • Local file path, preferably md、txt、html
  • For already extracted text docx / pdf
  • Comparison scenario: the user provides the "counterparty version" and "our template/redlines"
  • Review standards: company policies, approval matrix, transaction policy, legal playbook, standard templates

If the user only provides image scans, non-copyable PDFs, or scattered screenshots:

  • First try as much as possible to extract structured text
  • If extraction fails, clearly state that clause-by-clause review cannot be reliably performed, and request copyable text or excerpts of key clauses

Default settings

  • Default output language:zh-CN
  • Default mode:standard
  • Default risk posture:balanced
  • Default jurisdiction:中国大陆
  • Default output directory:contract-reviews/{slug}-{timestamp}/
  • Default signing recommendation: only give it when the evidence and key clauses are sufficient; otherwise output "needs more information before judgment"
  • Default order of review standards:
    1. Mandatory laws, regulations, and regulatory requirements
    2. Company policies, approval rules, contract templates, and redline lists provided by the user
    3. Industry practice and commercial common sense
    4. The general checklist built into this skill

If the user has not provided company policies or templates:

  • Continue to complete the general review
  • But must clearly mark "not checked against your company's internal policies"
  • May use the built-in standard redlines as a starting point for a general corporate position
  • Must not fabricate internal policies, approval authority, or redlines

If the user does not specify a jurisdiction and the contract falls within a Chinese enterprise transaction context:

  • Review by default under mainland China commercial contract standards
  • When data, personal information, cross-border transfer, trade secrets, labor, or consulting arrangements are involved, prioritize reading references/prc-defaults.md
  • In the final report, clearly mark "This review is by default conducted in the context of mainland China law; if the contract provides for foreign law or foreign dispute resolution, further review is required"

Review mode

Mode Applicable scenario Output depth
quick Quick mine-sweeping, only looking at obvious issues, tight timeframe High-risk issues + key revision suggestions
standard Default mode, most contract reviews Clause breakdown + risk register + review report
signing-gate High amount, high regulation, high dispute risk, or nearing signing Mandatory source verification + missing-item check + signing recommendation + items to be confirmed

Automatic determination rules:

  • When the user says "take a quick look," "do a preliminary scan first," or "no need to be too detailed," use quick
  • When the user mentions "signing immediately," "please give a conclusion on whether it can be signed," or "run through it according to company rules," at least use standard
  • When involving cross-border data transfer, exclusive intellectual property, exclusivity, huge liquidated damages, regulatory licenses, labor employment, high-value procurement, long-term SaaS, or major cooperation, escalate to signing-gate

Responsibilities of the five Agents

Do not actually write them as five disconnected answers; instead, work serially in this order and persist intermediate outputs to disk.

1. Planner Agent

Responsible for defining task boundaries and review standards.

At minimum confirm:

  • Contract type
  • Review objective: compliance, commercial, procurement, sales, delivery, data, IP, employment, signing gatekeeping
  • Transaction role: our side / counterparty / neutral
  • Whether there are our templates, company policies, approval matrix, red lines
  • Whether revision suggestions, alternative clauses, or signing conclusions are required
  • Timing requirements and version information

Output to 00-brief.md。

2. Clause Agent

Responsible for breaking the contract into "reviewable units"; do not directly mix comments into large blocks of body text.

Task:

  • Establish a clause directory and clause id
  • Identify key definitions, rights and obligations, amounts, terms, trigger conditions, exceptions, allocation of liability
  • Mark missing clauses, conflicting clauses, vague expressions, and blank variables
  • When necessary, split an unnumbered contract into C1、C2、C3 form

Output to 01-document-map.md and 02-clause-register.md。

3. Law Agent

Responsible for verifying the "basis" rather than drawing conclusions from experience.

Task:

  • Identify issues such as applicable jurisdiction, industry regulation, data compliance, anti-commercial bribery, export control, labor employment
  • Search and record laws and regulations, regulatory rules, judicial interpretations, and company policies provided by the user
  • For each basis, clearly write: source level, title, publication date/effective date, and its relationship to your review conclusion
  • Distinguish:
    • 违法/违规风险
    • 违反公司制度或审批要求
    • 市场惯例偏离

Under the default mainland China law scenario:

  • First read references/prc-defaults.md
  • General contract issues should first proceed from the contract part of the Civil Code of the People's Republic of China
  • When involving personal information, data processing, or cross-border transfer, first verify against PIPL, DSL, the current Cybersecurity Law, and Cyberspace Administration of China rules
  • When confidentiality, non-compete, technical materials, source code, or customer lists are involved, pay extra attention to trade secret and anti-unfair competition risks
  • When consultants, on-site staffing, or flexible employment are involved, pay extra attention to the risk of being reclassified as a labor relationship or creating employment compliance obligations

Output to 03-authority-log.md。

4. Risk Agent

Responsible for classifying issues, assigning severity levels, explaining consequences, and forming actionable handling recommendations.

Task:

  • Use references/risk-taxonomy.md 's classification and levels
  • Merge duplicate issues to avoid the same risk being recorded repeatedly across multiple clauses
  • Determine whether it is "must modify," "negotiable," "acceptable but must be acknowledged," or "insufficient information"
  • For each issue, provide:
    • Risk level
    • Risk category
    • Triggering clause
    • Basis
    • Impact
    • Recommended action

Output to 04-risk-register.md。

5. Report Agent

Responsible for turning review conclusions into deliverables that the business can use directly.

Task:

  • Use references/report-template.md to generate the final draft
  • Output an executive summary, key risks, recommended redlines, issues to be confirmed, and signing recommendations
  • If the user needs it, additionally generate a "non-legal-language summary for the business"

Output to 05-redlines.md and 06-review-report.md。

Output file

Create a directory for each task:contract-reviews/{slug}-{timestamp}/

  • source.md: The uniformly saved contract text or excerpts
  • 00-brief.md: Task boundaries, contract type, review standards, version information
  • 01-document-map.md: Contract metadata, structural overview, preliminary screening of missing items
  • 02-clause-register.md: Clause register
  • 03-authority-log.md: Laws and regulations, regulatory rules, company policies, template comparison basis
  • 04-risk-register.md: Risk register
  • 05-redlines.md: Proposed revision plan or alternative clauses
  • 06-review-report.md: Final review report
  • 07-open-questions.md: Issues with insufficient information or requiring business confirmation; generate only when needed

If the user only wants the answer in the chat window, still save by default 06-review-report.mdand provide the path in the reply.

Workflow

Step 1: Establish the review task and write it to 00-brief.md

Prioritize extracting from the current conversation; do not repeatedly ask about defaults. At minimum, clearly write:

  • Contract name and version
  • Contract type
  • Our role
  • Target jurisdiction or dispute resolution venue
  • Review mode
  • Whether there are company policies/templates/redlines
  • Whether alternative clauses are required
  • Whether a signing conclusion is required
  • Current information gaps

If the user has not clearly stated the contract type, first infer it from the clause content as one of the following:

  • nda
  • service
  • procurement
  • saas
  • license-ip
  • employment-consulting
  • data-processing
  • other

Step 2: Save the main text and build a document map

  1. Uniformly write the main text provided by the user to source.md
  2. Extract:
    • Contract name
    • Signing parties
    • Definition clauses
    • Commercial clauses
    • Liability clauses
    • Dispute resolution clauses
  3. Write 01-document-map.md
  4. When there are no clause numbers, assign to each reviewable unit C1、C2 identifiers such as
  5. Generate 02-clause-register.md

02-clause-register.md Recommended columns:

Clause ID Clause title Summary Issue type Preliminary Notes

Step 3: Based on retrieval and standards comparison, write into 03-authority-log.md

Execution principles:

  • First read references/source-hierarchy.md
  • Any conclusion directly related to legal liability, compliance obligations, data processing, licensing, labor, IP ownership, breach liability, or dispute resolution must be sourced
  • Time-sensitive content must have its publication date and effective date verified
  • Do not present "common market practice" as "legal requirement"
  • Company policies, templates, and approval authority tables provided by the user are internal constraints and must be marked separately

03-authority-log.md Suggested columns:

Authority ID Hierarchy Name Date Applicable point Notes

Step 4: Identify risks and write into 04-risk-register.md

Execution order:

  1. Scan the clause register item by item
  2. Use the contract type checklist to check for missing items
  3. In the mainland China context, then read the PRC-specific redline file for the corresponding contract type
  4. Map the issue to a risk category
  5. Assess severity, probability of occurrence, and remediability
  6. Form handling recommendations

04-risk-register.md Each issue must include at least:

  • risk_id
  • severity
  • category
  • clause_id
  • issue
  • basis
  • impact
  • recommended_action
  • fallback_position
  • owner_question(if business information is needed)

Step 5: Generate amendment recommendations and write into 05-redlines.md

When the user requests "give amendment recommendations," "give alternative clauses," or "revise according to our position," this must be generated.

Drafting requirements:

  • First read references/standard-redlines.md, determine priorities and fallback positions
  • If reviewed under mainland China law by default, additionally read the PRC-specific redline file for the corresponding contract type
  • When specific alternative wording is needed, then read references/clause-templates.md
  • Prioritize giving "why it should be changed" and "what to change it to"
  • Alternative clauses should be as directly pasteable into the contract as possible
  • When the jurisdiction or transaction background is unknown, do not fabricate highly specific legal language
  • If only directional suggestions can be given, clearly mark them as "clause direction suggestions" rather than directly signable text

Step 6: Generate a review report and write into 06-review-report.md

Must use references/report-template.md。

The report must clearly distinguish:

  • Clear illegal or non-compliant risks
  • Non-compliance with company policies or internal redlines
  • Commercial risks that are clearly unfavorable to us but negotiable
  • Points where information is insufficient and no conclusion can be drawn for now

Step 7: Form a signing recommendation

The signing recommendation may only output one of the following four categories:

  • 建议签署
  • 修改后可签
  • 暂不建议签署
  • 需补充信息后判断

Determination principles:

  • Existence of Critical and uncovered risks, usually 暂不建议签署
  • If there are major information gaps, output 需补充信息后判断
  • If the main issues are commercial negotiation items and there is a clear redline, output 修改后可签
  • Only when there are minor or acceptable deviations should you consider 建议签署

Writing standards for review conclusions

Each conclusion should follow this order as much as possible:

  1. First point out the clause or missing item
  2. Then write what the risk is
  3. Then write what the basis is
  4. Then write what consequences it will cause
  5. Finally give amendment recommendations or confirmation questions

Avoid these problems:

  • Only saying "there is risk" without saying where the specific risk is
  • Asserting illegality based only on experience without stating the basis
  • Presenting internal preferences as legal bottom lines
  • Giving extreme redlines detached from the transaction context
  • Giving overly strong conclusions when information is insufficient

Default tightening rules for high-risk matters

When the following matters are encountered, raise the review intensity by one level by default:

  • Uncapped liability, indirect losses, loss of profits, punitive liability
  • Perpetual exclusivity, default exclusivity, overly broad non-compete restrictions
  • Full assignment of intellectual property, unclear ownership of deliverables, background IP being dragged in
  • Large-scale personal information processing, cross-border transfers, overly broad audit rights
  • Unilateral termination, automatic renewal, unilateral price changes, missing acceptance standards
  • Severely back-loaded payment conditions, no security for advance payments, unequal set-off rules
  • Jurisdiction, arbitration seat, and governing law are extremely unfavorable to our side
  • Representations and warranties are too broad and exceed the scope we can control

Evidence and boundaries

  • This is a contract review workflow, not a substitute for formal legal opinions issued by a licensed lawyer
  • Do not package conclusions that have not been source-verified as certain judgments
  • When the full contract text has not been seen, clearly state that the conclusion is based only on the portion provided
  • If company policy conflicts with the law, first point out the legal conflict, then list internal process recommendations separately