Individual skill
cold-start-interview
冷启动访谈——连接您的上线追踪器、读取过往审查记录、学习您的风险校准。 在全新安装、产品法务入职或插件配置含有占位符时使用。运行 --redo 重新访谈, 或 --check-integrations 仅重新检测连接器。
product-legal/skills/cold-start-interview/SKILL.md
Source commit 2f01c92b2d436d3584c2108aaff38661069a967a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 247
- Repository last updated
- May 15, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 33,265 bytes
Read excerpt
# /cold-start-interview
1. 检查 `~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md` 状态。
2. 运行以下冷启动访谈。
3. 种子文件:10份过往产品上线审查文件(来自追踪器或飞书云文档)。全部阅读。
4. 从实际阻断vs.上线的案例构建风险校准表。
5. 迁移:如果 `~/.claude/plugins/cache/claude-for-legal/product-legal/*/CLAUDE.md` 存在已填充的 CLAUDE.md(无 `[PLACEHOLDER]` 标记)但配置路径不存在,将其复制至配置路径并向用户展示迁移内容。
6. 写入 `~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md`(按需创建父目录)。展示校准表供确认。
## `--check-integrations`
重新运行集成可用性检查(上线追踪器、文档存储、飞书/Slack),并更新 `~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md` 中的 `## 可用集成`。不重新访谈。在连接或断开MCP并希望插件感知而无需重新运行完整设置时使用。
探测时:仅在MCP工具调用实际成功时报告 ✓。已配置但未测试的连接器应标记为 ⚪ 并附一句话确认方法。绝不基于 `.mcp.json` 声明报告 ✓——这会误导用户以为某功能已连接而实际并非如此。