yanliudesign/offer-toolkit-skill / salary-negotiation-skill
salary-negotiation-skill
Verified| File | Kind | Size |
|---|---|---|
| .gitignore | other | 46 B |
| LICENSE | other | 1.0 KB |
| README.md | markdown | 9.0 KB |
| README.zh.md | markdown | 8.8 KB |
| SKILL.md | skill md | 12.1 KB |
| deal-bank/_deal-template.md | markdown | 2.6 KB |
| deal-bank/_index.md | markdown | 1013 B |
| examples/negotiation-report-template.html | other | 64.3 KB |
| frameworks/comp-benchmarks.md | markdown | 5.8 KB |
| frameworks/leverage-heuristics.md | markdown | 5.7 KB |
| frameworks/negotiation-report.md | markdown | 14.9 KB |
| frameworks/negotiation-tactics.md | markdown | 8.0 KB |
| frameworks/recruiter-playbook.md | markdown | 9.4 KB |
| prompts/counter-simulation.md | markdown | 12.9 KB |
| prompts/final-recommendation.md | markdown | 8.7 KB |
| prompts/leverage-map.md | markdown | 6.6 KB |
| prompts/negotiation-strategy.md | markdown | 7.5 KB |
| prompts/offer-diagnosis.md | markdown | 7.5 KB |
| prompts/script-generator.md | markdown | 11.0 KB |
prompts/final-recommendation.md
View on GitHub# Final Recommendation
**目标:** 谈判 playbook 最后一节。清晰给出 3 件事:**要什么** / **别推什么** / **何时停**。
这一节是整份 report 的**指挥棒** — 如果用户只读一节,就是这节。
**铁律**
- **必须有 stop-line**。谈判不是无限循环。没写 stop-line 的建议 = 把 offer 谈没了。
- **别墙头草**。用户情绪化时最需要一个明确的方向。"Depends on your risk tolerance" 是废话,你已经在 Step 2 收集了 risk tolerance,现在必须给结论。
- **量化 walk-away**。"如果他给不到 X,你走" 而不是"如果他给不了什么合理的数字,你走"。
---
## Step 1 · 输出格式(3 段)
### 段 1 · WHAT TO ASK FOR(要什么)
按 [`negotiation-strategy.md`](negotiation-strategy.md) 的 Modality + Strategy Table,浓缩成 **3-5 行 bullet**:
```
✅ Base: $210K → target $220K–$230K [priority 1]
✅ RSU: $600K → target $720K–$780K [priority 1]
✅ Sign-on: $50K → target $65K–$80K [priority 2]
❌ Bonus: 不要 push(Year 1 已 guaranteed)
❌ Title: 不要 push(Level 已合理)
```
每行必须:**当前数字 → target 区间 → priority tier**。
---
### 段 2 · WHAT NOT TO PUSH(别推什么)
**这一段是本 skill 最反直觉、最有价值的一段**。用户来找你都是"想要更多",但一半问题在"推错了地方"。
对每一项 offer 组件 + 每一个 negotiation lever,明确标 ❌ 不要推,并给 1 句为什么:
**典型 "别推" 清单**(按情况挑 3-5 条):
| 组件/杠杆 | 什么情况下 ❌ | 一句为什么 |
|---|---|---|
| **Base** | 已在 P75+ 或 band top | 你在 push 制度性硬 ceiling,只会消耗信用 |
| **Bonus target %** | 任何 mid-career 岗位 | Bonus % 是 Level 挂钩死数,不谈 |
| **Title / Level** | 无 down-level 争议 | 谈 title 会打断 comp 谈判节奏,进公司 6 个月内自然可 promo |
| **Stock refresh %** | 首次 offer 阶段 | Refresh 是 post-tenure 决定,谈判首轮谈 refresh = recruiter 觉得你不懂 |
| **PTO days** | 大厂 | 大厂 PTO 是 policy,unlimited 是幌子但改不了 |
| **Remote work** | 已经明确是 hybrid 的 role | policy 谈判会把整个 offer 推到 HR/legal 桌上,慢死且经常被拒 |
| **Start date > 3 个月** | 除非 visa 强制 | 招聘官 headcount 有季度 KPI,你推迟 = 他不 close 你 |
| **Additional equity vest acceleration** | 首次 offer | 只 senior + IPO 期公司特有的语言,用错了显得 amateur |
| **Second sign-on 加价(第 2 轮)** | Modality C/D | 你已经拿了一次 sign-on 补,第 2 轮再要 = greedy signal |
**输出格式**:
```
❌ Bonus target 别推 — 15% 是 IC5 死数,不是 negotiable
❌ Title 别推 — 你已经 Senior,谈判首轮谈 Staff 会打断 comp 讨论
❌ Refresh policy 别谈 — 首次 offer 阶段谈 refresh 是 amateur signal
❌ Start date 别拖超过 6 周 — Recruiter Q3 KPI 到 8/30,拖了会失去 momentum
```
---
### 段 3 · WHERE TO STOP(何时停)· 三条 stop-lines
明确 3 条硬线:**签的线** / **走的线** / **暂停冷静的线**。
**Stop-Line 1 · SIGN LINE(签的线)**
写清楚:如果 recruiter 给到什么,你**立刻签**(不再回第 3 轮)。
**判定原则**:
- Modality A(双开):达到 **80% of your target**(不是 100%)就签。原因:抓 80% 已经是漂亮 negotiation;抓 100% 时招聘官通常在等你多要一次好 rescind。
- Modality B(单点):达到 **90% of your target** 就签。原因:单点集中的谈判效率高,招聘官给到 90% 说明他真的 stretched。
- Modality C(收尾):**任何 non-zero improvement** 就签。你原本没 leverage,任何 delta 都是 gift。
**格式**:
```
SIGN 如果:
- Base 给到 $220K+ AND RSU 给到 $700K+/4yr
- OR Base 给到 $225K+ 单独(RSU 未动)
- OR RSU 给到 $780K+/4yr 单独(Base 未动)
→ 立即接受,回一句 "This works — I'm ready to sign. Please send the updated letter."
```
---
**Stop-Line 2 · WALK LINE(走的线)**
写清楚:如果 recruiter 拒绝到什么程度,你**走**。
**判定原则**:
- **有 competing offer 且 competing offer 明显更好** → walk line 是"低于 competing offer TC 10%"
- **有 competing offer 且 comparable** → walk line 是"低于当前 offer 5%(i.e., recruiter 想 downgrade)"
- **无 competing offer 但当前有稳定工作** → walk line 是"低于原 offer any component(recruiter 反悔)"
- **无 competing offer 且失业** → 基本没 walk line — 除非 recruiter 直接 rescind 或行为极端
**格式**:
```
WALK 如果:
- Recruiter 明确说 "we cannot make any adjustments" AND
- Base < $215K OR RSU < $650K/4yr(即达不到 walk-away floor)
→ 礼貌 walk:
"I really appreciate the time you and the team have invested. Given where the numbers land vs. what I need, I don't think I can move forward with this one. I hope we stay in touch."
```
---
**Stop-Line 3 · FREEZE LINE(暂停线)**
**这条最常被忽略**,也是新手最容易犯的错误。
用户情绪激动 / 谈判失控 / 被 recruiter push 到 emotional corner 时,**主动暂停 24 小时**,不当场决定。
**触发条件**:
- Recruiter 在电话里 push 你 "I need an answer today"
- 你自己发现你在 emotionally react(生气 / 委屈 / 兴奋过头)
- Recruiter 给了一个 unexpected 数字(比预期高很多 or 低很多),你的第一反应可能错
- Recruiter 用了 "we may need to reconsider" 这种威胁语言
**Freeze 脚本**:
```
FREEZE 如果:
- Recruiter 逼你当场答 OR
- 你自己感觉在情绪反应 OR
- 数字比预期偏离 15%+(任一方向)
→ 说:
"This is a significant decision, and I want to give it the thoughtfulness it deserves. Let me sleep on it and come back to you tomorrow morning with a firm answer. I appreciate you working through this with me."
然后挂电话 / 关邮件,24 小时不动。24 小时后回到本 report §3 Strategy 重新校准。
```
**Freeze 是最强的 non-obvious move**。招聘官几乎无法拒绝"我明天早上答复你",因为拒绝这句话会让他显得 unreasonable。
---
## Step 2 · Final Verdict(一句话)
Report 顶部会有一个 verdict,这里给它的最终版本:
**Modality A · 高 leverage**:
> **Overall: Aggressive Play — dual-track base + RSU push, target +15-25% TC. Sign at 80% of target. Walk if any downgrade. Deadline drift acceptable — recruiter needs you more than you need him.**
**Modality B · 中 leverage**:
> **Overall: Single-Front Push — pick RSU as main battle, target +10-15% TC. Sign at 90% of target. Walk if downgrade + competing offer worse than 5%. Move within 1 week.**
**Modality C · 低 leverage**:
> **Overall: Light-Touch Close — sign-on bump only, target +2-5% TC. Sign at any positive delta. Never walk (single offer, high need). Wrap within 3 business days.**
**Modality D · 不谈**:
> **Overall: Sign as-is — offer above market, no leverage, high personal need. Send acceptance today. Confirm sign-on/start date via 1 friendly email; if no changes, sign anyway.**
---
## Step 3 · 一份"Emergency Protocol"(放 §6 底部)
紧急情况的一页速查(照抄下面结构):
```
🚨 EMERGENCY PROTOCOL
如果 recruiter 说 "we need an answer in the next hour":
→ 说 "I need to review with my family / sleep on it — I'll respond by [tomorrow morning]." 别当场答。
如果 recruiter 说 "if you don't accept, we're pulling the offer":
→ 说 "I hear you. Given that timeline, let me confirm: are you saying the offer will be withdrawn if I don't accept by [time]? I want to be sure I understand."
→ 让他重复一次,让他听到自己在 rescind。90% 会 back off。10% 是真的 → 该 walk 就 walk。
如果 你反悔了想接受一个你已经 rejected 的 offer:
→ 立刻打电话(不要 email),说 "I've reflected on our conversation and would like to revisit if the door is still open."
→ 40% 情况下门还开着。别拖过 48 小时。
如果 recruiter 悄悄 downgrade 修改版 offer(vs 原 offer):
→ 说 "The updated offer is actually lower than the original on [component]. Was that intentional?" — 让他必须回答。80% 情况是"内部改错了",会回滚。
```
---
## Step 4 · 写完检查
**输出前自检**:
- [ ] SIGN / WALK / FREEZE 三条 stop-line 都写全了,数字明确
- [ ] "不推" 清单至少 3 条,每条有一句为什么
- [ ] Verdict 明确到 Modality,不是 "it depends"
- [ ] Emergency Protocol 段落照抄,不删
- [ ] 全程无"祝你好运" / "希望顺利" 这种废话
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |