Industry brief
Open-source AI workbench for interview prep: resume + JD to role intel, story bank, scripts, mock interviews, and live copilot.
npx -y skills add YunyueLi/greenroom --skill industry-briefAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generates industry and role reference reading (行业与岗位通识) for a target job — landscape, role expectations, must-know concepts, high-frequency interview topics, quotable viewpoints with sources — written to the workspace library/ folder. Use when the user asks for 行业通识 / 岗位认知 / 这个行业要懂什么 / 面这个方向需要补什么知识, or as step 4 of the greenroom full pipeline. Do NOT use for company-specific research (use job-intel) or answer scripts (use interview-script).
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.5 KB, as published. Nobody here has run it
industry-brief · 行业与岗位通识
为目标岗位生成一份可以反复阅读的参考材料，落在工作台 library/<行业-岗位>-通识.md。它解决的问题：候选人对岗位本身能讲清楚，但行业格局、岗位方向的高频概念、面试官默认你该知道的常识有缺口。
前置
- 读
jobs/<slug>/job.md和intel.md（知道行业、岗位方向、面试官背景）。 - 查本仓库
knowledge/目录：有没有现成的「行业 × 岗位」条目可以引用做底（有就引用 + 增量更新，没有就全新调研）。
调研与写作
用 web 搜索补齐，每条硬结论带来源链接，拿不准标「未核实」。结构：
---
title: <行业> · <岗位方向> 通识
updated: <date>
---
# <行业> · <岗位方向> 通识
## 行业格局
头部玩家、近 12 个月的关键变化、当前争论点（面试官爱用争论点出题）。
## 岗位画像
这个方向的人日常做什么、用什么衡量产出、和相邻岗位的边界。
## 必须能讲清的概念
8-15 个，每个两三句人话解释 + 一个会被追问的点。
## 高频面试话题
按出现频率排序，每个给出题角度（参考 knowledge/ 题型地图与公开面经，带来源）。
## 值得引用的观点
3-5 条来自头部从业者公开发言的判断，注明谁说的、哪里说的。面试中引用要消化成自己的话。
纪律
- 写的是参考阅读，不替用户表态；观点都注明出处，候选人自己决定信哪条。
- 篇幅 1500-3000 字，超了就砍：这是考前阅读材料，长到读不完等于没写。
- 通用知识沉淀：如果本次调研产出了
knowledge/还没有的通用内容（与候选人个人无关的行业/岗位知识），提示用户可以贡献回开源仓库。
收尾
汇报：写了哪个文件、覆盖了几个概念和话题、引用了几条来源；提示在控制台「资料」页阅读。