negotiate-a-job-offer
Skill0 starsChanged 4 days agoMITView on GitHub
Research what a job should pay, answer the salary expectations question, negotiate a job offer, compare two offers or decide on a counter-offer. Use for "how much should I ask for", "what are your salary expectations", "how do I negotiate my offer", "which offer should I take" or "should I accept a counter-offer".
In this repository17 other files it gives its agents.
- after-a-layoffSkill
- answer-application-questionsSkill
- choose-a-path-as-a-studentSkill
- find-career-directionsSkill
- follow-up-on-applicationsSkill
- future-proof-against-aiSkill
- go-public-after-a-layoffSkill
- informational-interviewsSkill
- plan-a-career-changeSkill
- prepare-for-interviewSkill
- return-to-work-after-a-breakSkill
- share-your-work-in-publicSkill
- start-a-new-jobSkill
- tailor-cv-to-jobSkill
- test-a-careerSkill
- update-linkedin-for-a-career-changeSkill
- write-cover-letterSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
If base pay is fixed, ask about one other thing that matters: start date, title, flexible days, training budget, sign-on payment or an …
- Distinctive: line 39
Never invent salary figures.
- Distinctive: line 40
Don't encourage bluffing about competing offers.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Negotiate a job offer
Pay conversations go best with a researched range, one clear request and a calm tone. The goal is a fair offer they can accept without regret, not winning.
Research the number first
- Start with official pay data for the occupation and area: the BLS Occupational Outlook Handbook or CareerOneStop in the US, the ONS Annual Survey of Hours and Earnings in the UK, or the national statistics office elsewhere.
- Add live evidence: pay ranges in current job posts for the same title, level and city, and what people in the role say.
- Set a range whose bottom is a figure they would genuinely accept.
"What are your salary expectations?"
Give the range, tied to the role: "Based on similar roles here, I'm looking for X to Y, depending on the full package." If it's asked very early, it's fine to ask what the budgeted range is first.
Negotiating an offer
- Thank them and ask for a day or two to review it in writing.
- Make one clear request backed by research: "Based on similar roles and my experience with X, I was hoping for Y. Is there flexibility?"
- If base pay is fixed, ask about one other thing that matters: start date, title, flexible days, training budget, sign-on payment or an early review.
- Get the final offer in writing before resigning anywhere.
Draft the actual message or talking points for them, short and polite.
Comparing two offers
Put them side by side in one table: total pay, the daily work, the manager, growth, flexibility, commute and stability. Weight each row by how much it matters to them, score it, and then check whether the winner matches their gut. If it doesn't, ask which row they'd really weight higher.
Counter-offers
Accepting a counter-offer makes sense only if pay was the main reason for leaving and the counter fixes it properly, in writing. If they started looking because of the work, the manager or progression, more money rarely fixes it.
Rules
- Never invent salary figures. Point to the sources above and say when a number is an estimate.
- Don't encourage bluffing about competing offers.
- Employment law and tax questions go to an official source or an adviser.
If the OffLadder tools are connected
browse_career_guides with topic interviews lists the pay and offer guides; find_career_guide answers one question, such as "how do I negotiate a job offer" or "compare two job offers", and read_career_guide returns it in full.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

