agentleFS
Sign inStart free
aksheywaksheyw/career-command-center-template/skills/salary-negotiate/SKILL.md

salary-negotiate

Skill1 starsChanged 4 months agoMITView on GitHub

Full salary negotiation prep — current comp, target, scripts, and counter-offer handling. Argument: [company name] [optional: offer details]

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the current employer counters, use the response template from career-tools.md.

    line 48
  2. Distinctive:

    Ask new company for signing bonus to cover notice buyout

    line 54
  3. Distinctive:

    Ask current employer for early release

    line 55
  4. Distinctive:

    Never give a number first — always ask for their range first

    line 60
  5. Very specific:

    Use the user's specific leverage argument from YOUR_PROFILE.md (illiquid equity, restricted vesting, etc.) if applicable

    line 62
  6. Distinctive:

    Always negotiate — base, signing, equity, title — even if you plan to accept

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are preparing the user for salary negotiation. Read ALL of the following before responding:

  • ${CLAUDE_PLUGIN_ROOT}/skills/resume-customizer/references/career-tools.md — full salary negotiation section including current comp template, target ranges by company type, scripts, counter-offer handling, notice-period negotiation
  • ${CLAUDE_PLUGIN_ROOT}/references/YOUR_PROFILE.md — current compensation context

STEP 1: Assess the situation

Based on the user's input, determine:

  • Company type (MNCs / Top Local / Growth Startup — adapt categories to user's geography)
  • What stage of negotiation: first offer / counter / final push
  • Whether an offer has been received or if preparing pre-offer

STEP 2: Output the full negotiation brief

CURRENT COMPENSATION CONTEXT

Pull from YOUR_PROFILE.md (Job Search Status → Current Compensation table). Include:

  • Base
  • Equity (units, value, liquidity status)
  • Vested / unvested percentages
  • Key point: any liquidity, restriction, or forfeit risk

TARGET RANGE FOR THIS COMPANY

Pull the correct target from career-tools.md based on company type. Match to the user's stated target from YOUR_PROFILE.md.

READY-TO-USE SCRIPTS

  • Script 1 — When asked "What are your salary expectations?": pull exact script from career-tools.md. Do not paraphrase.
  • Script 2 — When asked "What are you currently making?": pull exact script from career-tools.md. Focus on the user's leverage point (illiquid equity argument, restricted vesting, etc.).
  • Script 3 — When receiving an offer below target: pull counter-offer guidance from career-tools.md. Expand with company-specific framing.

WHAT TO NEGOTIATE BEYOND BASE SALARY

From career-tools.md: signing bonus (to cover unvested equity forfeit), equity, title, start date.

Calculate unvested forfeit value if an offer has been received. This is the minimum signing bonus to ask for.

COUNTER-OFFER HANDLING

If the current employer counters, use the response template from career-tools.md. Emphasize: the decision was about scope and growth, not compensation.

NOTICE-PERIOD STRATEGY

Pull from YOUR_PROFILE.md's notice period. Options:

  • Ask new company for signing bonus to cover notice buyout
  • Ask current employer for early release
  • Offset with unused PTO

NEGOTIATION PRINCIPLES (NON-NEGOTIABLE)

  1. Never give a number first — always ask for their range first
  2. Give a range, not a single number, when pressed
  3. Use the user's specific leverage argument from YOUR_PROFILE.md (illiquid equity, restricted vesting, etc.) if applicable
  4. Multiple processes = stronger position. Only mention if true.
  5. Always negotiate — base, signing, equity, title — even if you plan to accept

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free