菜单
Run the commercial-legal setup interview for the Legal Turkish adaptation. Builds a Turkish-law commercial contracts practice profile with playbook side, KVKK/data posture, Turkish notice methods, TL approval thresholds, renewal tracking, escalation matrix, and output guardrails.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
EU AI Act (ve Türkiye uyumu) per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".
Run an AI impact assessment — structured intake, risk analysis, regulatory classification per regime in scope, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed impact assessment in `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`. Use when user says "impact assessment for", "assess this AI use case", "run an AIA", "generate an AIA", "we need to document this AI system", "AI risk assessment for X", or follows a conditional triage result.
Run the cold-start interview — learns your AI governance practice and writes `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains `[PLACEHOLDER]` markers, or when user says "set up ai governance plugin", "onboard me", "configure ai governance".
Guided customization of your AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customize".
Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.
Diff a new AI regulation or guidance against your current governance posture — surfaces gaps, priorities, and a remediation plan with owners and deadlines. Use when an AI regulation moves (or you learn about one you missed), or when user says "new reg just dropped", "does [regulation] affect us", "gap analysis for EU AI Act (ve Türkiye uyumu)", "compliance check against [AI law or guidance]", or pastes regulatory text.
| name | cold-start-interview |
| description | Run the commercial-legal setup interview for the Legal Turkish adaptation. Builds a Turkish-law commercial contracts practice profile with playbook side, KVKK/data posture, Turkish notice methods, TL approval thresholds, renewal tracking, escalation matrix, and output guardrails. |
| argument-hint | [--redo] [--check-integrations] [--side sales|purchasing] |
İlk kurulum mülakatını çalıştırır ve ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md dosyasını yazar. Bu dosya bütün commercial skill'lerin okuduğu pratik profilidir.
Check current state. Read ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md.
--redo -> ask before overwriting.--side sales|purchasing -> ask only side-specific playbook questions.Use the template. Use plugin template commercial-legal/CLAUDE.md as the output scaffold.
Write only after review. Before writing, summarize open gaps and ask whether to leave placeholders.
Do not infer from ambient memory. Use only the user's answers and documents explicitly shared in this session.
Show summary and next steps. Offer a test review after writing.
--check-integrationsProbe only what can actually be tested. Do not mark an integration as connected merely because it is listed in .mcp.json.
Check:
Update ## Available Integrations in the user profile.
--side sales|purchasingRe-run only the matching playbook section:
sales: company sells goods/services; company is vendor/supplier.purchasing: company buys goods/services; company is customer/buyer.Leave the other side untouched. Update **Active side:**.
Say:
commercial-legalticari sözleşme işleri içindir: tedarikçi sözleşmeleri, SaaS/abonelikler, gizlilik sözleşmeleri, tadil geçmişi, yenileme/fesih takibi ve onay eskalasyonları.Kısa kurulum temel rol, taraf, yetki, entegrasyon ve varsayılan playbook alanlarını kurar. Tam kurulum gerçek playbook pozisyonlarınızı, TL onay eşiklerinizi, KVKK yaklaşımınızı, yenileme uyarılarınızı ve örnek imzalı sözleşmelerden çıkan kalibrasyonu ekler.
Kısa mı, tam mı ilerleyelim?
Wait for the answer.
Ask:
Ask:
Ask:
If sales or both, ask sales-side positions:
If purchasing or both, ask the same for purchasing-side.
Ask GREEN/YELLOW/RED positions for:
GREEN requires attorney-reviewed positions.
Ask:
Ask:
Ask whether matter workspaces are needed:
If on, ask cross-matter context default and confidentiality levels.
Ask for recent signed agreements or playbook documents:
Son 5-10 imzalı sözleşmeyi, playbook dokümanını veya onay matrisini paylaşabilirsiniz. Yoksa atlayabiliriz; eksikleri profilde açıkça işaretlerim.
Extract positions but mark anything uncertain as [verify] or [PLACEHOLDER].
Show:
## Kurulum Özeti
- Rol:
- Taraf:
- Ana playbook pozisyonları:
- Onay matrisi:
- KVKK yaklaşımı:
- Yenileme takibi:
- Açık kalan sorular:
Ask:
Bunları profiline yazayım mı? Açık kalan alanları placeholder olarak bırakabilirim.
Write to:
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
Use the template sections: