Build and deliver a raise request that actually works — the evidence, the number, the timing, and the exact words — instead of hoping it gets noticed.
SkillScore45Maintained
Automatic
◆HR & People Ops pack
Last verified 8/30/2026
What it changes
Passed 10 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill45%
Checks it passed that the model alone missed
Includes the section label `**The script**`.
Includes the section label `**The number:**`.
Omits apologetic phrases from the conversation script.
and 4 more in the full report
4 fixed6 passed either way12 still failing0 broke
Pass-rate lift
+18 pp
Tokens
+15%
Agent turns
0%
Response time
-21%
Model gemini-3.6-flashMeasured 8/30/2026v110 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
I'm a UX Designer making $80k. I revamped our main onboarding flow which increased user conversion by 18%. I want to ask my Design Director for a bump in pay, but I'm afraid of naming a specific salary number in case it's too high and turns them off. Market range for senior UX is $95k-$105k. Construct my pay raise proposal and script.
What was checked, without and with the skill
Checked
Without skill
With skill
Anchors the proposal to a single specific target salary figure.
Missed
Passed
Includes the section label `**The number:**`.
Missed
Passed
case-05 · gemini-3.6-flash · 8/30/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md60 linessingle file
Ask for a Raise
Raises rarely come from working hard and waiting to be noticed — they come from making a clear case at the right time to the right person. Most people either never ask or ask badly ("I've been here a while and could use more money"). This builds the version that works: evidence of your value, a specific justified number, good timing, the words to say, and answers to the pushback. It's a business case, not a plea.
What This Skill Produces
Your value case — your actual contributions, results, and added responsibilities, framed as value delivered (not effort spent)
A target number — a specific ask backed by your market rate and contribution, not a vague "a raise"
Timing & audience — when to ask (after a win, at review cycles, not during bad times) and who actually decides
The conversation script — how to open, state the ask, and hold, in words you'd actually say
Pushback responses — answers to "there's no budget," "not right now," "the market's tough," and how to get a concrete path if it's a no
Required Inputs
Ask for these if not provided:
Your contributions — what you've delivered, especially results and expanded scope since your last raise
Current pay & market rate — what you earn and what the role pays (benchmark it if unknown)
The context — company/team health, review cycles, your relationship with your manager
What you want — a number, and your walk-away/backup if it's no
Framework: Build The Case, Time It, Ask Clearly
Frame value, not effort. Managers pay for impact, not hours — lead with results, revenue/savings, and expanded responsibilities, quantified where possible.
Anchor to a real number. Combine your contribution with market rate into a specific ask; a vague request gets a vague answer.
Time it well. Ask after a clear win or at a review cycle, when budget and goodwill exist — not during layoffs or a bad quarter. And ask the person who actually decides.
Say it plainly and hold. Open with the value, state the number, then stop talking — let them respond. Confidence and a specific ask beat apology and hedging.
Handle the no. If it's not now, get a concrete path: what specifically would earn the raise, and by when — a vague "maybe later" is a soft no to pin down.
Output Format
Raise request: current [pay] → target [ask] · role [x]
Your value case: [contributions/results/added scope — as value delivered, quantified].
The number: [specific ask] — justified by [contribution + market rate].
Timing & who: [when to ask + the actual decision-maker].
The script
[Open with value] · [state the number] · [then stop and listen].
If they push back: "no budget" → [response] · "not now" → [get a concrete path: what + by when].
Extract and risk-rate hidden assumptions in a product brief or PRD. Use when asked to review a product brief for assumptions, audit a PRD for risks, find hidden assumptions, validate product plans, or run an assumption analysis. Produces a prioritised assumption map with confidence and impact scores, recommended validation methods, and critical assumption flags.