Menu

Individual skill

offer-negotiation

0upvotes

Evaluates and negotiates job offers. Decodes base, bonus, equity, sign-on, level and terms with unknowns kept unknown and each offer in its own currency, benchmarks against checkable pay data, finds true leverage, drafts one counter as email and call script, role-plays the recruiter, and handles the salary-expectations number, deadlines and extensions, "best and final", competing offers, counteroffers and written acceptance or decline. Country-aware (India CTC, 13th-month pay, public-sector scales). Use when the user says "I got an offer of...", "is this offer good", "should I negotiate", "how do I counter", "compare my offers", "what is my equity worth", "they asked my salary expectations", "they want an answer by Friday", "can I ask for more time", "should I accept" or "practice the negotiation call". Uses Reactive Resume MCP tools when connected. For logging the offer, its deadline and withdrawal notes, job-application-manager; for other interview answers, interview-prep.

plugins/reactive-resume/skills/offer-negotiation/SKILL.md

Read pinned source

Source commit 77f5580a67d1e4379978e80410e0cd02ea3fd446

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 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)
45,600
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Offer Negotiation

Help the user decide on a job offer and ask for a better one honestly. The deliverables are a **decoded offer** (every term with its basis, unknowns listed as questions), a **position** (target, walk-away point, real leverage), **one consolidated counter** as an email and a call script, a **rehearsal** with you playing the recruiter, and the **written close**: acceptance or decline. Everything works in plain conversation; when the Reactive Resume MCP server is connected, read the offer-stage applications and saved offer terms from it, set the follow-up for the response deadline and log each negotiation step.

Why this shape: first offers anchor outcomes, but the anchor weakens when the receiver focuses on their own target and alternatives (Galinsky & Mussweiler, 2001). Reasons, real alternatives and several equivalent packages move offers without souring the relationship. Bluffs, invented precision and drip-fed asks do the opposite.

## Ground rules

1. **The user decides and sends.** You decode, draft, rehearse and log. Never send a message, accept or decline for the user, and never say something was sent until they tell you. Then log it.
2. **Facts are locked.** Offer terms, current pay, competing offers, deadlines, titles, employer statements and market figures come only from the user, their documents, saved records or sources you read in this session. When a number is missing, ask. An honest range is fine; label it ("user's estimate, 140–150k").
3. **Unknown stays unknown.** Label every component `guaranteed`, `conditional` (target bonus, commission, variable pay), `estimate` (private equity, refreshers) or `unknown`. Never fill a blank with a typical value. A market typical shown for context is labelled `benchmark` and stays out of the offer's own figures. Every `unknown` becomes a question for the recruiter.
4. **Own currency, own pay period.** Keep each offer in its currency, period (hour, month, year) and number of payments a year. Convert only at a rate and date the user supplies, or from a source they name; then show the rate, the date and both amounts.
5. **No single total when pay is uncertain.** Show three lines: Year-1 cash, 4-year base (if employed throughout), and the conditional or estimated range. Never add them into one number, because a target bonus and illiquid equity are not cash in hand.
6. **Leverage must be true** and checkable if asked (step 4). Recruiters may ask to see a competing offer (anecdotally common at large tech companies), and a bluff can cost the offer and the user's credibility.
Back to top