Russian Legal Contract Review
Use this skill for practical first-pass legal review under Russian realities. It is legal-risk analysis, not a substitute for a licensed lawyer's final advice.
Current-Law Gate
Russian law and Roskomnadzor practice change often. Before giving a current legal answer, verify the applicable text live or state that the answer is not current-verified.
When the task depends on current law, cite the source, act name/number, article or clause, and редакция/date. Do not rely only on model memory or a copied old text.
Read references/sources.md when the user asks about statutes, Роскомнадзор, персональные данные, ГК РФ, 152-ФЗ, 149-ФЗ, 143-ФЗ, or "последние изменения".
Intake
Identify or ask for the missing facts that change the risk analysis:
- our side: заказчик, исполнитель, продавец, покупатель, правообладатель, лицензиат, оператор ПДн, обработчик;
- counterparty status: ООО, ИП, самозанятый, физлицо, иностранная компания;
- B2B, B2C, employment, agency, license, SaaS, services, sale, marketplace, advertising, data processing;
- applicable law, jurisdiction, venue, arbitration clause, mandatory претензионный порядок;
- data flows: categories of ПДн, subjects, purposes, storage location, processors, cross-border transfer, biometrics, data allowed for dissemination;
- money and paperwork: price, НДС, withholding, currency, invoices, acts, УПД, EDI, e-signature, acceptance;
- intellectual property: exclusive/non-exclusive license, alienation, work made for hire, source code, models, content, trademarks.
If "143-ФЗ" appears in a Roskomnadzor/personal-data context, treat it as ambiguous. Clarify whether the user means 149-ФЗ, 152-ФЗ, 242-ФЗ/localization, or the actual 143-ФЗ cited in the document.
Review Workflow
- Check document completeness: title, parties, реквизиты, dates, exhibits, referenced policies, blank fields, signatures, attachments.
- Classify the document and our side before calling a term "bad" or "market".
- Map mandatory Russian-law issues with
references/checklists.md.
- Separate legal risk from business risk and operational risk.
- Prefer concrete rewrites over abstract advice.
- Mark unresolved assumptions explicitly.
Output
For document review, use:
Короткий вывод: whether it is signable, signable after fixes, or not ready.Критичные блокеры: terms that can make the deal unenforceable, illegal, impossible to operate, or materially unsafe.Таблица рисков: clause, risk, why it matters under РФ context, proposed fix.Что переписать: ready-to-paste Russian wording when possible.Вопросы перед подписанием: only questions that materially affect the conclusion.Источники: links and редакция/date for laws or official guidance used.
For compliance/personal-data questions, add:
- operator/processor role;
- lawful basis and consent need;
- RKN notification status;
- localization and cross-border transfer;
- privacy policy and consent texts;
- breach/incident duties;
- security measures owner: legal, organizational, technical.
Boundaries
- Do not invent court practice, RKN positions, or article numbers.
- Do not present unofficial blogs as law; use them only for orientation and verify against primary or authoritative sources.
- Do not give tax, criminal, labor, or regulated-industry conclusions as final without flagging the need for specialist review.
- Do not keep large statutory excerpts in the skill. Laws must be checked live.
1---2name: ru-legal-contract-review3description: Use when reviewing Russian-law contracts, offers, policies, personal-data/Roskomnadzor compliance, or legal wording for Russian businesses; triggers include РФ, ГК РФ, 152-ФЗ, 149-ФЗ, РКН, ПДн, договор, оферта, NDA, SaaS, license, service agreement.4license: MIT5---67# Russian Legal Contract Review89Use this skill for practical first-pass legal review under Russian realities. It is legal-risk analysis, not a substitute for a licensed lawyer's final advice.1011## Current-Law Gate1213Russian law and Roskomnadzor practice change often. Before giving a current legal answer, verify the applicable text live or state that the answer is not current-verified.1415When the task depends on current law, cite the source, act name/number, article or clause, and редакция/date. Do not rely only on model memory or a copied old text.1617Read `references/sources.md` when the user asks about statutes, Роскомнадзор, персональные данные, ГК РФ, 152-ФЗ, 149-ФЗ, 143-ФЗ, or "последние изменения".1819## Intake2021Identify or ask for the missing facts that change the risk analysis:2223- our side: заказчик, исполнитель, продавец, покупатель, правообладатель, лицензиат, оператор ПДн, обработчик;24- counterparty status: ООО, ИП, самозанятый, физлицо, иностранная компания;25- B2B, B2C, employment, agency, license, SaaS, services, sale, marketplace, advertising, data processing;26- applicable law, jurisdiction, venue, arbitration clause, mandatory претензионный порядок;27- data flows: categories of ПДн, subjects, purposes, storage location, processors, cross-border transfer, biometrics, data allowed for dissemination;28- money and paperwork: price, НДС, withholding, currency, invoices, acts, УПД, EDI, e-signature, acceptance;29- intellectual property: exclusive/non-exclusive license, alienation, work made for hire, source code, models, content, trademarks.3031If "143-ФЗ" appears in a Roskomnadzor/personal-data context, treat it as ambiguous. Clarify whether the user means 149-ФЗ, 152-ФЗ, 242-ФЗ/localization, or the actual 143-ФЗ cited in the document.3233## Review Workflow34351. Check document completeness: title, parties, реквизиты, dates, exhibits, referenced policies, blank fields, signatures, attachments.362. Classify the document and our side before calling a term "bad" or "market".373. Map mandatory Russian-law issues with `references/checklists.md`.384. Separate legal risk from business risk and operational risk.395. Prefer concrete rewrites over abstract advice.406. Mark unresolved assumptions explicitly.4142## Output4344For document review, use:4546- `Короткий вывод`: whether it is signable, signable after fixes, or not ready.47- `Критичные блокеры`: terms that can make the deal unenforceable, illegal, impossible to operate, or materially unsafe.48- `Таблица рисков`: clause, risk, why it matters under РФ context, proposed fix.49- `Что переписать`: ready-to-paste Russian wording when possible.50- `Вопросы перед подписанием`: only questions that materially affect the conclusion.51- `Источники`: links and редакция/date for laws or official guidance used.5253For compliance/personal-data questions, add:5455- operator/processor role;56- lawful basis and consent need;57- RKN notification status;58- localization and cross-border transfer;59- privacy policy and consent texts;60- breach/incident duties;61- security measures owner: legal, organizational, technical.6263## Boundaries6465- Do not invent court practice, RKN positions, or article numbers.66- Do not present unofficial blogs as law; use them only for orientation and verify against primary or authoritative sources.67- Do not give tax, criminal, labor, or regulated-industry conclusions as final without flagging the need for specialist review.68- Do not keep large statutory excerpts in the skill. Laws must be checked live.
ThomasMoreAI