PluginBench
Skill
Review
Audit score 70

writing-job-descriptions

refoundai/lenny-skills

Write effective job descriptions by defining 12-month success and identifying candidate spikes.

What is writing-job-descriptions?

This skill helps you craft job descriptions that attract the right candidates by focusing on business impact and specific competencies rather than task lists. Use it when creating a job posting, defining a new role, or preparing to hire.

  • Define success by 12-month business impact instead of daily tasks
  • Identify the one or two areas where a candidate must excel (the 'spike')
  • Frame requirements as outcomes and progress rather than arbitrary feature lists
  • Use polarizing language to filter for candidates who thrive in your environment
  • Iterate job descriptions based on actual candidates you meet
  • Avoid generic language that attracts generic candidates

How to install writing-job-descriptions

npx skills add https://github.com/refoundai/lenny-skills --skill writing-job-descriptions
Claude Code
Cursor
Windsurf
Cline

How to use writing-job-descriptions

  1. 1.Ask yourself: what will be different about the business 12 months after this hire succeeds?
  2. 2.Identify the one or two areas where this person absolutely must excel
  3. 3.Replace task lists and 'years of experience' requirements with specific capabilities and outcomes
  4. 4.Determine what signals and language will attract your ideal candidate and filter out poor fits
  5. 5.Draft the description focusing on progress to be made, not arbitrary responsibilities
  6. 6.Iterate the description as you meet candidates and learn what the market actually offers

Use cases

Good for
  • Creating a new job posting for an open position
  • Defining an emerging role based on high-performer feedback
  • Rewriting a stale job description that isn't attracting qualified candidates
  • Clarifying role expectations before starting a hiring process
  • Filtering candidates by environment fit (pace, urgency, work style)
Who it's for
  • Hiring managers and team leads
  • Founders and executives building teams
  • Product leaders defining new functional roles
  • HR professionals writing job postings
  • Anyone preparing to hire for a new position

writing-job-descriptions FAQ

Should I list all the tasks this person will do?

No. Focus on what will be different about the business because of this hire, not daily tasks. Job descriptions that are just task lists attract generic candidates and miss the actual progress the role enables.

How specific should I be about required experience?

Replace 'X years of experience' with specific capabilities. Instead of '5 years of Excel,' say 'ability to build PowerPoints for executive alignment.' Time is just a proxy for capability—name the actual capability you need.

Can I use polarizing language in a job description?

Yes, intentionally. Language like 'high pace, long hours, candidates must thrive under urgency' filters for people who actually want that environment. Generic language attracts generic candidates.

Should I iterate my job description after posting it?

Yes. Treat it like a product. Meet candidates, learn what the market offers, and refine the role definition. The best descriptions evolve based on real candidates you encounter.

What if I'm not sure what success looks like?

Start by imagining 12 months later: you hired well, the person thrived, and you're celebrating. What changed about the business? That's your success metric. Build the description backward from that outcome.

Full instructions (SKILL.md)

Source of truth, from refoundai/lenny-skills.


name: writing-job-descriptions description: Help users write effective job descriptions. Use when someone is creating a job posting, defining a new role, preparing to hire, or trying to attract the right candidates for an open position.

Writing Job Descriptions

Help the user write effective job descriptions using frameworks and insights from 6 product leaders.

How to Help

When the user asks for help with job descriptions:

  1. Define success first - Ask what success looks like 12 months after the hire, not what tasks they'll do
  2. Identify the spike - Determine the one or two areas where this person needs to excel (not everything)
  3. Write for progress - Frame the role around the progress to be made, not a list of arbitrary tasks
  4. Consider the signal - Discuss whether the language attracts or repels the right candidates

Core Principles

Start with 12-month success

Jonathan Lowenhar: "Start with, it's 12 months later, you hired the person, 12 months have gone by, you're clinking champagne because of how great it's been. What's changed about the business?" Define success by business impact after one year, not a list of responsibilities.

Job descriptions are made up

Bob Moesta: "Job descriptions are made up. They're literally just made up - a list of stuff the manager wants plus stuff they don't want to do." Focus on the 'progress' the role enables rather than arbitrary feature requirements.

Identify where they should spike

Lauren Ipsen: "Trying to determine where this person should major and minor, where they should spike. Is this someone that's going to lean into design efforts or operate like a very senior PM?" Define specific competencies required rather than seeking a generalist who does everything.

Frame requirements as outcomes

Bob Moesta: "Don't tell me I need Excel, PowerPoint, and Word skills. Tell me what I'm going to do with those. Tell me you're going to need to build PowerPoints for executive alignment." Replace 'X years of experience' with specific capabilities that time is supposed to represent.

Iterate based on candidates

Jason Shah: "Taking a product mindset where I meet people and don't know exactly what role they're going to fill. A product mindset on hiring and iterating on it based on the candidates you're meeting." Treat job descriptions as iterative documents that evolve with market reality.

Use polarizing language intentionally

Anton Osika: "Long hours, high pace, candidates must thrive under high urgency. Those seeking comfortable work need not apply." High-signal, polarizing language filters for candidates who thrive in specific environments.

Codify emerging roles

Peter Deng: "I asked her to write up a job description of what this thing is. There's something magical here. The role was model designer." Ask high-performing individuals to write their own ideal job description to identify new functional needs.

Questions to Help Users

  • "If this hire is wildly successful, what will be different about the business in 12 months?"
  • "What is the one thing this person absolutely must be great at?"
  • "What are you describing as requirements that are actually just proxies for something else?"
  • "Who do you want to attract with this language, and who do you want to filter out?"
  • "Is this role solving a specific problem, or is it a collection of tasks no one wants?"
  • "What would 'making progress' look like for this person in their first 6 months?"

Common Mistakes to Flag

  • Lists of tasks instead of outcomes - Focus on what will be different because of this hire, not what they'll do daily
  • Requiring generalists - Identify specific spikes; trying to find someone good at everything finds no one
  • 'Years of experience' as a proxy - This tells candidates nothing about what they'll actually need to do
  • Static descriptions - Iterate on the role definition after meeting candidates and understanding the market
  • Bland language - Generic job postings attract generic candidates; be specific and even polarizing

Deep Dive

For all 9 insights from 6 guests, see references/guest-insights.md

Related Skills

  • Conducting Interviews
  • Evaluating Candidates
  • Onboarding New Hires
  • Building Team Culture