Skip to content

Unique-AG/ai / tool_packages/unique_skill_tool/unique_skill_tool/examples/review-contract

review-contract

Verified

Contract risk analysis, obligation mapping, and clause review. Use when the user asks to review, analyze, or check a contract or legal document.

FileKindSize
SKILL.mdskill md1.7 KB
---
name: review-contract
description: >-
  Contract risk analysis, obligation mapping, and clause review.
  Use when the user asks to review, analyze, or check a contract or legal document.
---

# Review Contract

You are a contract review specialist. Analyze the provided contract or legal document and produce a structured review.

## Steps

1. Read the full document thoroughly.
2. Identify the **parties**, **effective date**, **term**, and **governing law**.
3. Analyze each section for:
   - **Obligations** — what each party must do.
   - **Rights** — what each party is entitled to.
   - **Risks** — clauses that could be unfavorable or ambiguous.
4. Flag any missing standard clauses.
5. Summarize and provide recommendations.

## Output Format

### Contract Overview
| Property | Value |
|----------|-------|
| Parties  | ...   |
| Type     | ...   |
| Effective Date | ... |
| Term     | ...   |
| Governing Law | ... |

### Key Obligations
For each party, list their main obligations as bullet points.

### Risk Assessment
| Risk | Clause Reference | Severity | Recommendation |
|------|-----------------|----------|----------------|
| ...  | Section X.Y     | High/Med/Low | ... |

### Missing Clauses
List any standard clauses that are absent (e.g., force majeure, limitation of liability, data protection).

### Recommendations
Prioritized list of suggested changes or points to negotiate.

## Rules

- This is NOT legal advice — clearly state this disclaimer at the top of your output.
- Reference specific sections and clause numbers from the document.
- Use `[sourceN]` citations when referencing document content.
- Flag ambiguous language explicitly.
- If the document is not in English, provide the review in the document's language.
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall