$ loading_
Run the cold-start interview to learn your IP practice and write your practice profile. Use on first install when the practice profile is missing or still contains placeholders, when re-onboarding with --redo, or when re-probing integrations with --check-integrations after connecting or disconnecting an MCP. This is the ONLY skill that should run on a fresh install.
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "cold-start-interview" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/ip-legal/skills/cold-start-interview/SKILL.md 2. 保存为 ~/.claude/skills/cold-start-interview/SKILL.md 3. 装好后重载技能，告诉我可以用了
Runs the cold-start interview. First run writes ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md; subsequent runs with --redo re-interview and show a diff before overwriting.
Check current state: Read ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. If it contains [PLACEHOLDER] or [Your Company Name], proceed with fresh interview. If populated and --redo not passed, ask: "Looks like you're already set up. Want to re-run the interview? This will overwrite ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md (I'll show you a diff first)."
Follow the interview script below.
Ask for practice documents: portfolio list (or IP management export), brand guidelines, C&D template(s), enforcement playbook, OSS policy. Accept file paths, Google Drive links, or IP-management record IDs.
Read the shared documents and extract actual positions — enforcement thresholds, approval chain, brand watch settings, OSS rules. Note deltas between stated positions and what templates/playbooks actually require.
Migration: If a populated CLAUDE.md (no [PLACEHOLDER] markers) exists at ~/.claude/plugins/cache/claude-for-legal/ip-legal/*/CLAUDE.md but not at the config path, copy it to the config path and show the user what was migrated.
Write ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md (create parent directories as needed) per the structure below. Use the lawyer's own words where possible.
Seed the portfolio register if the user shared a portfolio export or IP management system access: write to ~/.claude/plugins/config/claude-for-legal/ip-legal/portfolio.yaml. If nothing was shared, leave a placeholder pointer the portfolio tracker can fill later.
Show summary + propose next steps:
~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md is written. What did I get wrong?"--check-integrationsRe-runs the integration availability check (IP management system, patent research, legal research, document storage, Slack) and updates ## Available integrations in ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. Does not re-interview. Use when you connect or disconnect an MCP and want the plugin to notice without rerunning the full setup.
When probing: only report ✓ if an MCP tool call actually succeeded. Configured-but-untested connectors should be marked ⚪ with a one-line how-to for confirming. Never report ✓ based on .mcp.json declarations alone — that misleads users into thinking something is wired up when it isn't.
/ip-legal:cold-start-interview
/ip-legal:cold-start-interview --redo
/ip-legal:cold-start-interview --check-integrations
You are meeting this IP practice for the first time. Your job is to learn how they do IP work — not how IP is done in the abstract — and write what you learn into a living practice profile (the plugin config) that every other skill in this plugin reads before it does anything.
The lawyer should leave this conversation feeling like they just onboarded a sharp new paralegal who asked exactly the right questions. They should never see a YAML config file. They should see a document about their practice that they can edit in plain English.
Read ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md:
<!-- SETUP PAUSED AT: --> → greet the user and offer to resume from that section.…
Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
Drafts board or committee meeting minutes in your house format. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.