salary-negotiator
Skill22 starsChanged 3 months agoMITView on GitHub
Coaches a candidate or employee through compensation negotiation — researching market ranges, anchoring, countering an offer, negotiating the full package (base, bonus, equity, signing, benefits), and scripting the conversation. Use this skill when a user asks to "negotiate my salary", "I got a job offer, what do I say", "counter this offer", "ask for a raise", "how much should I ask for", or wants email/script wording for a comp conversation.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- JayRHa/agent-skillsword for word, first seen Oct 15, 2026
- landedjobs/ai-job-hunt-ostheir own version, first seen Jul 24, 2026
- JayRHa/AgentSkillsword for word, first seen Jun 9, 2026
Other versions3 projects use a version of this.
Word for word · 2
- JayRHa/agent-skills★ 12100% same
- JayRHa/AgentSkills★ 12100% same
Edited · 0
None found.
Wrote their own version · 1
- landedjobs/ai-job-hunt-os★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository194 other files it gives its agents.
- 0-templateSkill
- ab-test-analyzerSkill
- academy-guideSkill
- add-to-my-skillsSkill
- adr-authorSkill
- ai-tools-setupSkill
- algorithmic-artSkill
- api-and-interface-designSkill
- api-designerSkill
- api-docs-writerSkill
- apple-store-submitSkill
- aws-cost-optimizerSkill
- bash-script-hardeningSkill
- blog-post-writerSkill
- book-summarizerSkill
- branch-cleanupSkill
- brand-copy-landingSkill
- brand-copySkill
- brand-designSkill
- brand-guidelinesSkill
- browser-testing-with-devtoolsSkill
- canvas-designSkill
- changelog-generatorSkill
- changelog-keeperSkill
- chart-chooserSkill
- ci-cd-and-automationSkill
- ci-fix-loopSkill
- claude-apiSkill
- cloudflare-block-countriesSkill
- coderabbitloopSkill
- code-review-and-qualitySkill
- code-reviewerSkill
- code-simplificationSkill
- codexloopSkill
- comms-notionSkill
- comms-slackSkill
- comms-whatsappSkill
- competitive-analysisSkill
- concept-explainerSkill
- constraint-driven-developmentSkill
- context-engineeringSkill
- context-repoSkill
- cover-letter-writerSkill
- crash-courseSkill
- cron-schedulerSkill
- data-digestSkill
- data-pipeline-architectSkill
- debug-detectiveSkill
- debugging-and-error-recoverySkill
- decision-matrixSkill
- dependabot-triageSkill
- dependency-upgraderSkill
- deprecation-and-migrationSkill
- dev-instantdbSkill
- discernment-nudgeSkill
- doc-coauthoringSkill
- dockerfile-proSkill
- docs-index-keeperSkill
- documentation-and-adrsSkill
- docxSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 28
Never name the first number if you can avoid it: If asked expectations, deflect to "what's the range for this role?" If forced, anchor with …
- Distinctive: line 31
Negotiate collaboratively: Use "we" framing, silence after the ask, and trade — if base won't move, pivot to signing bonus, equity, or an …
- Distinctive: line 32
Get the final deal in writing: before resigning anything.
- Distinctive: line 51
Use silence: After you state a number, stop talking.
- Distinctive: line 52
Get everything in writing: before resigning.
- Distinctive: line 56
Disclosing your current salary or target first: when you don't have to.
≈ “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
Salary Negotiator
Overview
This skill helps a user negotiate compensation with confidence and tact — whether it's a new job offer or an internal raise. It covers market research, what's actually negotiable, anchoring, counter-offer math, and word-for-word scripts that stay collaborative rather than adversarial.
Keywords: salary negotiation, compensation, job offer, counter offer, raise, equity, RSU, signing bonus, total comp, benefits, anchoring, BATNA, ask for more money.
When to use vs. not
Use this when a user has (or is about to get) an offer, wants a raise, or needs scripting for a comp conversation. This skill gives strategy and wording, not live market data — always tell the user to verify ranges against current sources (levels.fyi, Glassdoor, Payscale, Levels, local salary surveys) for their role, level, and location near the conversation date.
Inputs to gather first
- The full current offer / current comp — base, bonus, equity, signing, benefits, not just base.
- Role, level, location (remote vs. on-site changes the market).
- The user's target and walk-away numbers, and their BATNA (other offers, staying put).
- Leverage: competing offers, in-demand skills, internal value, how badly they need this job.
- Stage: verbal offer, written offer, or annual review.
Workflow
- Establish the market range. Have the user pull comparables for their exact role/level/location. Define a defensible range; place the target near the top third. See
references/market-research.md. - Map the full package. List every negotiable lever — base, annual bonus %, equity/RSUs, signing bonus, start date, vacation, remote, title, review timing. Base isn't the only knob. See
references/levers.md. - Know your BATNA and walk-away. The strongest negotiator is willing to walk. Define the alternative and the lowest acceptable total comp before talking.
- Never name the first number if you can avoid it. If asked expectations, deflect to "what's the range for this role?" If forced, anchor with a researched range whose bottom is your real target.
- Get the offer in writing, then express genuine enthusiasm and a counter: "I'm excited about this — I was hoping we could get the base closer to $X." Anchor high but defensible.
- Counter on the strongest lever first, with a reason (market data, competing offer, scope). Bundle 2–3 asks so there's room to concede gracefully. See
references/scripts.md. - Negotiate collaboratively. Use "we" framing, silence after the ask, and trade — if base won't move, pivot to signing bonus, equity, or an early review.
- Get the final deal in writing before resigning anything. Confirm every component.
Decision framework
| If… | Then… |
| You have a competing offer | Lead with it (honestly) — it's the strongest lever |
| Base is capped by band | Pivot to signing bonus, equity, title, or a 6-month review |
| You're underpaid internally | Use market data + documented impact; request a specific number |
| Offer already meets target | Make one modest ask; don't over-negotiate a great offer |
| They say "this is final" | Test once politely; then decide against your walk-away, not your ego |
Worked example
See examples/counter-offer.md for a full counter-email and the reasoning behind each ask.
Best Practices
- Always negotiate a job offer — most have built-in room, and not asking leaves money on the table.
- Anchor with research, not feelings. Tie every number to market data or scope.
- Negotiate total comp, not just base.
- Stay warm and collaborative — you'll work with these people.
- Use silence. After you state a number, stop talking.
- Get everything in writing before resigning.
Common Pitfalls
- Accepting on the spot out of excitement or fear.
- Disclosing your current salary or target first when you don't have to.
- Negotiating against yourself by lowering your ask before they respond.
- Threatening or ultimatums ("match this or I walk") unless you mean it.
- Forgetting non-base levers (equity, signing, remote, vacation).
- Burning goodwill with an aggressive or entitled tone.
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.

