본문으로 건너뛰기
cccskills
무료GitHub에 공개

ask-for-a-raise

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. Use when asked how do I ask for a raise, I deserve more money, prepare me to ask for a raise, or negotiate a pay increase at my job. Produces a value case built on your actual contributions and market rate, a specific target number with justification, the right timing and person, a script for the conversation, and responses to the likely pushbacks — turning 'I want more' into a business case your manager can say yes to.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

  1. Frame value, not effort. Managers pay for impact, not hours — lead with results, revenue/savings, and expanded responsibilities, quantified where possible.
  2. Anchor to a real number. Combine your contribution with market rate into a specific ask; a vague request gets a vague answer.
  3. 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.
  4. 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.
  5. 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].

Quality Checks

  • The case is framed as value/impact, not effort or need
  • The ask is a specific number backed by contribution + market rate
  • Timing and the right decision-maker are addressed
  • A clear, confident script is provided
  • Responses to the common pushbacks are included
  • A "get a concrete path" plan exists for a no

Anti-Patterns

  • Asking based on need or tenure ("I've been here 3 years") instead of value.
  • A vague ask with no number.
  • Bad timing (during layoffs, to the wrong person).
  • Apologizing or over-hedging the ask.
  • Accepting a vague "maybe later" with no path.

Example Trigger Phrases

  • "How do I ask for a raise? I think I deserve more."
  • "Prepare me to negotiate a pay increase."
  • "Help me build a case for a raise and what to say."
  • "I want to ask for more money — what number and when?"
  • "My manager said 'no budget' last time. How do I approach it now?"

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

mohitagw15856의 스킬 모두 보기

이 스킬의 문제 신고