Agent skill · Workflow & Productivity

raise-vs-jump

Model staying for annual raises vs job-hopping for bigger bumps — cumulative earnings trajectories, the crossover year, and the costs the salary math hides (vesting resets, promotion paths, search risk). Use when asked should I switch jobs for more money, is job hopping worth it, model my salary if I stay vs leave, or raise versus new offer. Produces the year-by-year salary and cumulative-earnings table, the crossover year, and the not-in-the-model checklist that usually decides it.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorships scriptsMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill raise-vs-jump --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 5 KB
Bundled scripts: yes
Path: skills/raise-vs-jump/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Raise vs Jump Skill "Job hoppers earn more" is true on salary and incomplete on everything else: equity that vests on a cliff you keep resetting, the promotion you were two quarters from, the months of search time, the reputation cost of a short-stint résumé. This skill runs the salary math properly — trajectories, not single offers — and then insists on the checklist of what the salary math can't see, because that checklist decides more of these choices than the compounding does. ## What This Skill Produces - **The trajectory table** — year-by-year salary and cumulative earnings for both paths - **The crossover year** — when cumulative jump-earnings pass cumulative stay-earnings - **The gap at horizon** — final salary gap and cumulative gap, on stated assumptions - **The not-in-the-model checklist** — scored for this user's actual situation ## Required Inputs Ask for these if not provided: - **Current salary** and **realistic stay-raise %** — their employer's actual recent raises, not the poster in the break room (default 3%, labeled) - **Jump assumptions** — bump per jump (default 15%), years between jumps (default 3), raises between jumps (default 2% — jumpers often land at th

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Programmatic Helper
  4. Framework: What the Salary Math Hides
  5. Output Format
  6. The Trajectories
  7. What the Table Says
  8. The Checklist the Table Can't See
  9. The Honest Read
  10. Quality Checks
  11. Anti-Patterns
Ships with 2 files
  • references/worked-example.md
  • scripts/raise_vs_jump.py
Commands it runs
python3 scripts/raise_vs_jump.py --salary 120000
python3 scripts/raise_vs_jump.py --salary 120000 --stay-raise 3.5 --jump-bump 18 --jump-every 3 --json
More from pm-claude-skills
All skills →
About this skill
What does the raise-vs-jump skill do?

Model staying for annual raises vs job-hopping for bigger bumps — cumulative earnings trajectories, the crossover year, and the costs the salary math hides (vesting resets, promotion paths, search risk). Use when asked should I switch jobs for more money, is job hopping worth it, model my salary if I stay vs leave, or raise versus new offer. Produces the year-by-year salary and cumulative-earnings table, the crossover year, and the not-in-the-model checklist that usually decides it.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill raise-vs-jump --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going