negotiating-offers

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill negotiating-offers
0 commentsdiscussion
summary

Negotiate job offers and compensation using strategies from product leaders.

  • Focuses on identifying success factors beyond salary (tech debt, headcount, budget) and negotiating for those before discussing compensation
  • Emphasizes collaborative language (\"Are you open to...?\") and live conversations with hiring managers over email negotiations
  • Helps distinguish whether salary is the real goal or a proxy for respect, learning, autonomy, or growth
  • Suggests alternative arrangements l
skill.md

Negotiating Offers

Help the user negotiate job offers and compensation using strategies from 3 product leaders.

How to Help

When the user asks for help negotiating an offer:

  1. Understand their situation - Ask about the offer details, what they're hoping for, and what leverage or alternatives they have
  2. Reframe beyond salary - Help them think about what they need to succeed in the role, not just personal compensation
  3. Prepare the approach - Guide them on the right language, timing, and framing for the negotiation
  4. Coach on execution - Help them practice the actual conversation and anticipate responses

Core Principles

Negotiate for success factors before compensation

Phyl Terry: "Before we talk about money, I want to think about the things that will set me up to succeed. There's $10 million of tech debt here - are we on board that this will be priority one?" Identify critical blockers (tech debt, headcount, budget) during the interview process and ask for specific authority to fix them as part of the offer negotiation.

Use collaborative language - "Are you open to...?"

Phyl Terry: "87% of the time when you ask for more money, you get it. Say 'Are you open to $X? That's what I was hoping for. Is that something we can talk about?'" Conduct the negotiation live (phone or in-person) with the hiring manager if possible. Use "Are you open to...?" to keep the conversation collaborative and lower-risk.

Understand what you're really optimizing for

Bob Moesta: "Compensation is often a surrogate for other needs like respect or learning. I can pay people less if I give them better experiences." Before negotiating aggressively on salary, identify if you're really seeking money or something else (learning, autonomy, respect, growth). Sometimes the right move is to accept less money for better experience.

Consider alternative arrangements

Paul Millerd: "A big move is turning your current job into a contract job - employers are more open than people think. Say 'I want to work three days a week as a contractor. Are you open to this?'" If flexibility matters more than maximizing salary, propose specific alternative arrangements. Frame the reduced risk for the employer as a benefit.

Questions to Help Users

  • "What's the full offer - base, equity, bonus, and other terms?"
  • "What do you actually need to succeed in this role that you might not get by default?"
  • "Is salary the thing you really care about, or is it a proxy for something else?"
  • "What's your alternative if this negotiation doesn't work out? Do you have other offers?"
  • "Have you done the live conversation yet, or is it still over email?"
  • "What specific number or terms are you hoping to get to?"

Common Mistakes to Flag

  • Only negotiating salary - The resources, authority, and support you need to succeed are often more valuable than a few thousand in comp
  • Negotiating only over email - Live conversations build relationship and are more effective. Request a call with the hiring manager
  • Using adversarial language - "Are you open to...?" is more effective than demands or ultimatums
  • Not asking at all - Most of the time when you ask for more, you get it. The risk of asking is lower than most people think
  • Optimizing for the wrong thing - Make sure you know if you really want more money or if salary is a proxy for respect, growth, or autonomy

Deep Dive

For all 4 insights from 3 guests, see references/guest-insights.md

Related Skills

  • Building a Promotion Case
  • Finding Mentors & Sponsors
  • Career Transitions
  • Having Difficult Conversations
how to use negotiating-offers

How to use negotiating-offers on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add negotiating-offers
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill negotiating-offers

The skills CLI fetches negotiating-offers from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/negotiating-offers

Reload or restart Cursor to activate negotiating-offers. Access the skill through slash commands (e.g., /negotiating-offers) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.658 reviews
  • Yuki Abbas· Dec 12, 2024

    negotiating-offers is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Yuki Kim· Dec 8, 2024

    negotiating-offers reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Evelyn Abbas· Nov 27, 2024

    We added negotiating-offers from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Layla Taylor· Nov 11, 2024

    Useful defaults in negotiating-offers — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Rahul Santra· Nov 3, 2024

    Useful defaults in negotiating-offers — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yuki Li· Nov 3, 2024

    Keeps context tight: negotiating-offers is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Evelyn Sanchez· Nov 3, 2024

    Registry listing for negotiating-offers matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Pratham Ware· Oct 22, 2024

    Registry listing for negotiating-offers matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Yusuf Chawla· Oct 22, 2024

    We added negotiating-offers from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Yuki Gupta· Oct 22, 2024

    Useful defaults in negotiating-offers — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 58

1 / 6