customize-11

Guided customization of your privacy practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, DPA playbook, privacy policy commitments, PIA house style, DSAR process, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my playbook", or "customize".

インストールへ移動

リポジトリ: ThomasMoreAI/legal-skills-open
ソースの最終更新活動: 2026年6月1日 17:27
検出された SKILL.md の言語: 英語
スター: 40
フォーク: 4

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。

npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill customize-11

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md

ソースの指示 · 読み取り専用プレビュー

検索に戻るインストールに戻る

fetching-arbitration-rules

Use when retrieving arbitration institutional rules (ICC, LCIA, SCC, SIAC, HKIAC, VIAC, МКАС/МАК при ТПП України, UNCITRAL) — fetching current version, verifying redaction applicable to the date of arbitration agreement, constructing URLs for official rule texts

2026-06-12

determining-pl-request-regime

Use when choosing the Polish legal regime for letters, requests, applications, complaints, petitions, public-information requests, KPA filings, PPSA complaints, RODO access requests, registry extracts, court-file access, tax/ZUS/cudzoziemcy/USC procedures, or professional lawyer letters. Prevents mixing UDIP, KPA, PPSA, RODO, registry, special-procedure, and advocate/radca letter regimes.

2026-06-12

applying-new-york-convention

Use when preparing applications for recognition and enforcement of foreign arbitral awards in Poland, applications for setting aside arbitral awards under KPC art. 1205–1211, or opposing such applications — mapping Article V of the 1958 New York Convention to art. 1214–1215 of the Polish KPC, identifying grounds for refusal, structuring public policy arguments

2026-06-12

このリポジトリのすべてを見る

/customize

When this runs

The user typed /privacy-legal:customize. They want to change something in their privacy profile — a risk posture, an escalation contact, a DPA position, a PIA section, a DSAR timeline — without re-running the whole cold-start interview and without hand-editing YAML.

What to do

Read the config. Read ~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md (and ~/.claude/plugins/config/claude-for-legal/company-profile.md one level up). If the plugin config does not exist or still contains [PLACEHOLDER] values, say:

You haven't run setup yet. Run /privacy-legal:cold-start-interview first — customize is for adjusting a profile you already have.
Show the customizable map. List what's in the profile, grouped, with a one-line summary of the current value:
- Company / who you are — name, industry, jurisdictions, stage, practice setting, controller vs. processor orientation (shared across all 12 plugins — changes flow through company-profile.md)
- Risk posture — conservative / middle / aggressive, what each means for processor obligations, cross-border transfers, and retention
- People — DPO, privacy team, engineering liaison, outside counsel, escalation chain
- DPA playbook — positions on sub-processor notice, deletion, audit, liability, international transfers, SCCs — as processor and as controller
- Privacy policy commitments — the commitments your privacy notice has made that /policy-monitor watches practice against
- PIA house style — section order, risk scoring, stakeholder framing, when DPIA triggers apply
- DSAR process — verification, statutory timelines per regime, exemption application, template response structure
- Workflow — intake path, matter workspaces, policy-monitor sweep cadence
- Integrations — document storage / privacy tool / Slack status, fallbacks
Ask what they want to change.

What would you like to adjust? Pick a section, or describe the change in your own words.
Make the change. Show the current value, ask for the new value, explain what changes downstream, confirm, write it to the config.

Examples:
- Sub-processor notice 30 days → 14 days: "/dpa-review will now flag anything shorter than 14 days as a deviation. Existing DPAs stay as logged."
- New DSAR exemption in the playbook: "/dsar-response will surface this exemption in the assessment step where the facts match."
- Risk posture middle → conservative: "I'll flag more activities for PIA escalation, recommend stricter SCC clauses, and be more conservative on retention."
For shared-profile changes (company name, industry, jurisdictions, practice setting, stage): write to ~/.claude/plugins/config/claude-for-legal/company-profile.md and note:

This change affects all 12 plugins — any plugin that reads your jurisdiction footprint now sees [new value].
Close.

Done. Your next output will reflect the change. Anything else? You can run /privacy-legal:customize anytime.

Guardrails

Never delete a section. If the user wants to "remove" a regime from scope, offer to mark it [Not currently in scope] and explain what flagging drops.
Flag internal inconsistency. If the change would make the profile inconsistent (e.g., "processor only" + controller playbook positions active; or "no EU nexus" + SCCs in the default template), flag the tension.
Flag guardrail degradation. The [review] flag, source attribution tags, [verify] tags on cited regulations, and the DPIA-trigger mandatory-check on /use-case-triage are load-bearing — do not remove. If statutory DSAR timelines are adjusted below the regulatory minimum, refuse and explain why.
One change at a time. Don't re-ask the whole interview.

name	customize-11
title	/customize
description	Guided customization of your privacy practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, DPA playbook, privacy policy commitments, PIA house style, DSAR process, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my playbook", or "customize".
author	anthropics
author_url	https://github.com/anthropics/claude-for-legal/tree/main/privacy-legal/skills/customize
license	Apache-2.0
version	0.1.0
execution_mode	open

name	customize-11
title	/customize
description	Guided customization of your privacy practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, DPA playbook, privacy policy commitments, PIA house style, DSAR process, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my playbook", or "customize".
author	anthropics
author_url	https://github.com/anthropics/claude-for-legal/tree/main/privacy-legal/skills/customize
license	Apache-2.0
version	0.1.0
execution_mode	open

customize-11

ソース情報

インストール方法

ソースファイルを確認

このリポジトリの他の Skills

このリポジトリの他の Skills

/customize

When this runs

What to do

Guardrails