目标研究
Faaz172026-10-25查看 619复制 732
研究一家目标公司,并将档案写入共享/公司/——他们实际构建的内容、实习生将加入哪个团队、最近的具体新闻以及与候选人的重叠。在撰写任何首次联系电子邮件之前、在决定一家公司是否值得瞄准或在准备面试时使用。
📘如何使用这个技能
- 1复制技能内容·点击上方「Copy SKILL.md」复制全部内容,或 Download 下载到本地
- 2打开你的 AI 客户端·支持 Claude Code、Trae、Cursor、ChatGPT、DeepSeek、Kimi 等任意 AI 助手
- 3粘贴为系统提示/知识文件·Claude Code:放入 .claude/skills/ 目录;普通对话:作为首条消息发送并说「请严格按这份技能文档执行」
- 4直接提出你的需求·AI 会按技能定义的工作流、格式和约束来处理,无需再解释背景
💡 提示:技能生效后,每次对话只需一句需求,AI 会按 SKILL.md 的流程执行。
SKILL.md3318 chars
--- name: target-research description: Research a target company and write a dossier into shared/companies/ — what they actually build, which team an intern would join, recent specific news, and the overlap with the candidate. Use before writing any first-contact email, when deciding whether a company is worth targeting, or when preparing for an interview. --- # /target-research, build the company dossier Usage: `/target-research Space42` · `/target-research "Technology Innovation Institute" --for "<Person Name>"` The dossier is what makes paragraph 1 of the email possible. Without it, there is only a template with a name pasted in. ## Steps 1. **Check for existing work.** Read `shared/companies/<slug>.md` if it exists. If it was researched inside the last month, refresh the recent-news section rather than starting over. Also run `/obsidian-find <company>` — the vault may already know something. 2. **Add the company to `shared/targets.md`** if it is not there. 3. **Read the candidate's `evidence.md` before searching.** The point is to find overlap, and it is much easier to spot overlap when the search already knows what to look for. 4. **Delegate the search to the `company_researcher` agent.** It has the full method. It reads job postings before marketing pages, because job postings are where the real stack is written down. 5. **Look specifically for:** - Open engineering roles, including senior ones. They list the stack - The engineering blog, GitHub org, published papers - Whether they run an internship programme and through what route - One recent, dated, specific, linkable event - Which team the candidate would plausibly sit in 6. **Write the dossier** to `shared/companies/<slug>.md` in the format specified in `agents/company_researcher.md`. 7. **Assign a tier** and record why: - **Tier 1** — strong technical overlap, plausible route in, worth a properly researched email - **Tier 2** — real overlap but a harder route, or a less exact fit - **Tier 3** — worth an application through their formal process, not worth a cold email 8. **Say if the answer is no.** A company with no overlap or no reachable route is a legitimate finding. Recording it stops the next session repeating the search. ## Output format ``` ## Researched: <company> — Tier <n> **What they build:** <two sentences of engineering reality> **Stack:** <from job postings> **Team to target:** <name> **Takes interns:** yes | no | formal programme only | unknown **Paragraph-1 material** - <specific recent fact> — <URL> (as of YYYY-MM) **Overlap with <person>** | They need | <person> has | Strength | |---|---|---| **Angle:** <one sentence> **Gaps:** <what could not be verified> **Recommendation:** cold email | formal application | skip **Next:** /find-contact <company> ``` ## Rules - Job postings before marketing pages. Always. - Date every unstable fact. Team structures and funding move quarterly. - Never invent a recent event. "No recent public activity found" is a real answer and it changes the angle rather than blocking it. - Mark inferences as inferences. - Do not research companies not on the target list. Add them there first so the list stays honest. - One dossier per company, shared by both people. The overlap section gets a subsection per person.