anbeime/skill / skills/legal-assistant-skills-main/contract-review
contract-review
Verified律师助理与法律助手、项目管理专家在审核合同、排查条款风险时必备。自动执行基础、商业、法律三层审查,仅添加批注不改原文,一键生成带批注合同、审查摘要、综合意见及业务流程图,让合同风控与业务梳理更高效专业。
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 11.1 KB |
| SKILL.md | skill md | 5.4 KB |
| references/checklist.md | markdown | 5.3 KB |
| references/examples.md | markdown | 5.5 KB |
| references/flowchart.md | markdown | 1.8 KB |
| references/language.md | markdown | 2.0 KB |
| references/opinion.md | markdown | 1.3 KB |
| references/summary.md | markdown | 2.8 KB |
| references/technical.md | markdown | 2.7 KB |
| scripts/__init__.py | script | 50 B |
| scripts/contract_analyzer.py | script | 9.2 KB |
| scripts/document.py | script | 11.3 KB |
| scripts/error_handling.py | script | 16.3 KB |
| scripts/mermaid_renderer.py | script | 6.9 KB |
| scripts/ooxml/__init__.py | script | 189 B |
| scripts/ooxml/pack.py | script | 3.5 KB |
| scripts/ooxml/unpack.py | script | 1.1 KB |
| scripts/ooxml/validate.py | script | 1.7 KB |
| scripts/ooxml/validation/__init__.py | script | 433 B |
| scripts/ooxml/validation/base.py | script | 1.5 KB |
| scripts/ooxml/validation/docx.py | script | 311 B |
| scripts/ooxml/validation/pptx.py | script | 274 B |
| scripts/ooxml/validation/redlining.py | script | 217 B |
| scripts/opinion_renderer.py | script | 4.2 KB |
| scripts/summary_renderer.py | script | 9.1 KB |
| scripts/utilities.py | script | 3.1 KB |
| scripts/workflow.py | script | 59.2 KB |
references/summary.md
View on GitHub# Contract Summary Extraction
Objectively summarize the contract’s basic content to help legal teams understand the agreement quickly. **Do not provide risk assessments or legal advice.**
Default output is a DOCX rich-text file (`合同概要.docx` for Chinese, `Contract_Summary.docx` for English). Font defaults to Fangsong; adjust `summary_font` for non‑Chinese languages.
**Language rule:** output in the contract’s language. See **[language.md](language.md)** for selection rules and label mappings.
## Output Format
I. Basic Contract Information
Item Content
Contract Name [Extract title or designated name]
Contract Type [e.g., Sales, Services, Lease]
Parties Party A: [Name, Address]
Party B: [Name, Address]
Signing Date [Signature date]
Term [Start/end date or performance period]
Contract Amount [Total amount & currency; include installment schedule if any]
II. Business Model Overview
Brief description: [1–2 paragraphs summarizing the core transaction and relationship]
III. Key Clause Elements
3.1 Transaction Elements
Element Details
Subject Matter/Services [Goods, services, or deliverables]
Quantity/Specs [Quantity, model, technical specs]
Pricing Structure [Unit price, total price, adjustment mechanism]
Payment Terms [Payment ratio, milestones, method]
Delivery Terms [Location, time, acceptance standards]
3.2 Rights and Obligations
Party A main rights/obligations:
[Main rights]
[Main obligations]
Party B main rights/obligations:
[Main rights]
[Main obligations]
3.3 Performance Safeguards
Clause Type Details
Liability/Default [Consequences for each party]
Guarantees/Security [Deposit, guarantee, etc.]
Acceptance Standards [Procedure, criteria, dispute handling]
Quality Warranty [Warranty period, responsibilities, after-sales]
3.4 Risk Allocation & Special Terms
Risk Allocation:
[Force majeure clause]
[Risk transfer trigger]
[Loss allocation]
Special Terms:
[Intellectual property]
[Confidentiality]
[Exclusivity]
[Other special conditions or restrictions]
3.5 Dispute Resolution & Termination
Item Details
Dispute Resolution [Negotiation, mediation, arbitration, litigation & jurisdiction]
Amendment [Conditions and procedure]
Termination [Triggers, procedure, consequences]
Governing Law [Applicable laws/regulations]
IV. Key Timeline Milestones
[List key milestones in chronological order: signing, payment, delivery, acceptance, etc.]
## Output Requirements
- **Objectivity**: only extract and describe clauses; no subjective judgments
- **Completeness**: if a clause is missing, write “Not specified”
- **Accuracy**: faithfully reflect the contract text; quote critical wording when needed
- **Conciseness**: 500–800 words (simple), 800–1200 (standard), 1200–1500 (complex)
- **Structure**: strictly follow the above format for quick navigation
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |