salary-negotiator
Prepare and execute compensation negotiations with market data, scripts, and counter-offer strategy.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- salary-negotiator
- category
- career
- description
- Prepare and execute compensation negotiations with market data, scripts, and counter-offer strategy.
03 SKILL.md 正文
Overview
Almost every offer is negotiable, and the first number is rarely the last. Yet most candidates accept the first offer because negotiating feels confrontational. This skill reframes negotiation as collaborative problem-solving: you and the employer both want you to sign, and the only question is the package. It covers research, anchoring, scripts for every stage, and the counter-offer trap.
When to use
-
Evaluating a written offer and deciding whether/how to negotiate
-
Answering "what are your salary expectations?" early in a process
-
Juggling multiple offers for leverage
-
Negotiating a raise or promotion internally
-
Handling exploding offers and deadlines
Core concepts
-
-
- Never give the first number if you can avoid it. "What's your expected salary?" → "I'd like to understand the full scope first — what's the budgeted range for this role?" Whoever anchors first sets the frame.
-
-
-
- Negotiate the total package. Base, bonus, equity/RSUs, sign-on, relocation, remote flexibility, start date, title, review timeline. A "no" on base often becomes a "yes" on sign-on or equity.
-
-
-
- Market data is your leverage. Levels.fyi, Glassdoor, Pave, peer conversations — come with a range, not a feeling. "Based on market data for this role in this market, I'm targeting X-Y."
-
-
-
- Silence is a tactic. After you state your ask, stop talking. The urge to fill silence with concessions is the most expensive habit in negotiation.
-
-
-
- Get it in writing. Verbal promises evaporate. Every agreed term — including start dates and review timelines — goes into the written offer before you sign.
-
-
-
- The walk-away number. Decide your minimum acceptable package before negotiating. Without it, you'll rationalize a bad deal in the moment.
-
Practical workflow
-
-
- Research. Gather 3+ data points for the role, level, and market. Note the full range, not just the median — you negotiate against the top of the band, not the middle.
-
-
-
- Set your numbers. Three figures: ideal (ask), target (happy to sign), walk-away (decline). Keep the walk-away private; it's your discipline tool.
-
-
-
- Deflect early salary questions. Use the range-request script. If forced, give a wide, research-backed range with the top at your ideal — never a single number, never your current salary (it's irrelevant and often illegal to ask for).
-
-
-
- Evaluate the written offer. Score each component against your numbers. Identify the 2-3 levers with the most upside (usually base + sign-on + equity).
-
-
-
- Make the counter. One consolidated ask, framed collaboratively: "I'm excited about the role and the team. Based on my research and the scope, I'd be able to sign at [X base, Y sign-on]. Can we get there?" Then silence.
-
-
-
- Handle the pushback. Expect "this is our best offer" (often not true), "the band doesn't allow it" (ask about sign-on/equity, which often sit outside bands), or a split-the-difference. Respond to each calmly, one round at a time — 2-3 rounds is normal.
-
-
-
- Close cleanly. Once terms are agreed, confirm in writing, thank everyone, and stop negotiating. Post-acceptance renegotiation burns bridges.
-
Common pitfalls
-
-
- Accepting the first offer. The first offer is a starting point by design. A polite counter almost never rescinds an offer — that fear is the employer's best negotiating tool.
-
-
-
- Negotiating against yourself. "I was thinking maybe around X, but I'm flexible..." — you've just lowered your own anchor. State the ask and stop.
-
-
-
- Revealing your current salary. It anchors you to your past, not your market value. Deflect: "I'd prefer to focus on the market rate for this role."
-
-
-
- Only negotiating base. Candidates leave tens of thousands on the table ignoring sign-on bonuses, equity refreshers, and remote stipends.
-
-
-
- Using a fake competing offer. Lies get discovered and destroy trust. Real leverage only — even "I'm in late stages elsewhere" must be true.
-
-
-
- Exploding-offer panic. "Sign by Friday or it's gone" is usually negotiable: "I'm very interested — I need until [date] to make a thoughtful decision." Employers who truly want you will wait a few days.
-
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).