Agent Skills RU

Install

mkdir -p ~/.claude/skills
cp -R skills/ru-legal-contract-review ~/.claude/skills/

This is third-party code. Review the repository files before installing.

What it does

The pack currently holds one ready skill, ru-legal-contract-review. It makes the agent first establish our side, counterparty status, personal data flows and money terms, then check the contract against a Russian-law checklist. Before any conclusion about current law the agent must verify the statute against a source and cite the revision, or say plainly that it did not. Output follows a fixed shape: short verdict, critical blockers, risk table, ready-to-paste rewrites and questions before signing.

Who it is for. For lawyers, founders and product teams who need a quick first-pass review of a contract or policy under Russian rules.

Example request

Review this services agreement: we are the contractor, the counterparty is an LLC, and client personal data is processed

Limitations

This is risk analysis, not a substitute for a lawyer's final advice. The skill stores no statute texts and requires live checks, so without web access the agent will mark current-law conclusions as unverified. Other areas mentioned in the repository description are not published yet.

How to disable. Delete the ru-legal-contract-review folder from ~/.claude/skills or ~/.codex/skills; for other agents remove the matching rules file.

Security check

• The skill consists only of instructions and checklists
• Conclusions need a lawyer's review

README in short

The README presents the repository as a reusable skill pack: canonical text lives in skills, per-agent wrappers in adapters. One skill is published, for contract review under Russian law with a focus on the Civil Code, 152-FZ, 149-FZ and 242-FZ. Install for Codex and Claude Code is a folder copy, other agents use the adapters. MIT license.

SKILL.md

---
name: ru-legal-contract-review
description: 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.
---

# 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

1. Check document completeness: title, parties, реквизиты, dates, exhibits, referenced policies, blank fields, signatures, attachments.
2. Classify the document and our side before calling a term "bad" or "market".
3. Map mandatory Russian-law issues with `references/checklists.md`.
4. Separate legal risk from business risk and operational risk.
5. Prefer concrete rewrites over abstract advice.
6. Mark unresolved assumptions explicitly.

Related