vendor-agreement-review

Review vendor agreements for Russian law compliance and generate risk flags and redlines.

17|4|Updated May 25, 2026
One-click install
npx skills add https://github.com/AlsKozlov/ru-legal --skill vendor-agreement-review-alskozlov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vendor-agreement-review
Source: https://github.com/AlsKozlov/ru-legal/tree/main/packs/contract-law/skills/vendor-agreement-review
Command: npx skills add https://github.com/AlsKozlov/ru-legal --skill vendor-agreement-review-alskozlov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing vendor agreements for compliance with Russian law is time-consuming, error-prone, and often misses critical jurisdiction-specific risks that can render contracts unenforceable, such as missing essential terms, invalid liability caps, or improper intellectual property transfer clauses.

Core Features & Use Cases

  • Risk Flagging & Redlining: Identifies deviations from internal team playbooks, classifies risks by severity (red/yellow/green), and generates specific, actionable redlines instead of vague revision suggestions.
  • Russian Law Specific Compliance Checks: Covers all critical RF-specific rules including essential terms for service (Chapter 39), contract (Chapter 37), and supply (Section 3 of Chapter 30) agreements, limit of liability traps under Civil Code Article 401, dual indemnity mechanisms (Articles 431.2 and 406.1), IP transfer requirements under Article 1295, 152-FZ personal data protection rules, tax agent obligations, and sanctions compliance.
  • Use Case: A legal team can use this skill to review a new IT services vendor agreement, automatically flag missing essential terms that would make the contract unenforceable under Civil Code Article 432, and get pre-drafted redlines for liability and IP clauses aligned with Russian legal practice.

Quick Start

Use the vendor-agreement-review skill to analyze the attached vendor services agreement against the team's contract playbook and generate a full risk memo with prioritized redlines and escalation recommendations.

Frequently Asked Questions about vendor-agreement-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a vendor agreement for Russian law compliance risks?

To review a vendor agreement for Russian law compliance, validate essential terms under Civil Code Chapters 37, 39, and 30, check liability caps under Article 401, and verify IP transfer rules. This process flags unenforceable clauses and generates specific redlines to correct deviations from legal playbooks.

What are the critical IP transfer and personal data rules in Russian vendor contracts?

Critical Russian vendor contract rules include IP transfer requirements under Civil Code Article 1295 and personal data protection mandates under 152-FZ. Reviewing these rules ensures proper intellectual property assignment and strict data handling compliance, preventing invalid transfers and regulatory penalties.

How do I redline liability and indemnity clauses under Russian Civil Code?

Redlining liability and indemnity clauses under Russian Civil Code involves checking liability cap enforceability under Article 401 and validating dual indemnity mechanisms under Articles 431.2 and 406.1. This identifies invalid risk allocations and generates surgical revisions aligned with Russian legal practice.

Does automated contract review cover sanctions compliance and tax agent obligations?

Automated contract review does cover sanctions compliance and tax agent obligations. It scans vendor agreements to identify restricted parties and validate tax clauses, generating severity-classified risk flags that highlight sanctions exposure and non-compliant tax provisions.

Can I use this for mixed service and supply agreements under Russian law?

Yes, you can use this for mixed service and supply agreements under Russian law. The review applies to service, contract, supply, and mixed vendor agreements, validating essential terms across Chapter 39, Chapter 37, and Section 3 of Chapter 30 to ensure full enforceability.

What is the best way to generate a structured legal risk memo for vendor contracts?

The best way to generate a structured legal risk memo is to classify agreement deviations by severity and map them to specific redlines. This creates a prioritized review document with escalation recommendations, accelerating vendor contract approval workflows for legal teams.