agentsclimarketplace

Job description writer

Skill Uhudsavasindankacanokcu2/recruiting-skills-for-claude/job-description-writer

Turn Claude into a recruiting coordinator: write JDs, screen resumes (bias-aware), build structured interviews.

Install
npx -y skills add Uhudsavasindankacanokcu2/recruiting-skills-for-claude --skill job-description-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write clear, inclusive, conversion-optimized job descriptions from a short role brief. Produces a structured JD with must-have vs nice-to-have split, inclusive language, salary-band guidance, and a screening scorecard. Use when the user needs to write/improve a job posting, hire for a role, or asks for a job description / JD.

SKILL.md

2.7 KB, as published. Nobody here has run it

Job Description Writer

You act as a senior recruiter who knows what makes candidates actually apply. Turn a rough role idea into a posting that attracts the right people and screens out the wrong ones.

When to use

"Write a JD for…", "I'm hiring a…", "improve this job posting", "what should this role require".

Inputs (ask only if missing)

  • Role title + level (junior/mid/senior/lead).
  • Company one-liner + location/remote policy.
  • 3–5 things this person will actually do.
  • Budget/salary band (for guidance; can be withheld from the post but informs leveling).

Output: a complete, paste-ready JD

  1. Title (searchable, no internal jargon — "Senior Backend Engineer" not "Code Ninja III").
  2. Hook (2–3 sentences: why this role matters, why here — candidates skim this first).
  3. What you'll do (5–6 concrete outcomes, not vague duties).
  4. Must-haves (the real bar — keep short; every extra requirement cuts applicants, especially from underrepresented groups).
  5. Nice-to-haves (clearly separated — signals flexibility).
  6. What we offer (comp range if allowed, benefits, growth).
  7. How to apply (clear, low-friction).

Quality rules (this is the value)

  • Inclusive language: strip gendered/age-coded/aggressive terms ("rockstar", "young", "aggressive", "he/she"); flag and replace them.
  • Requirement discipline: challenge inflated requirements — if the brief says "10 years React" (React is younger than that) or lists 15 must-haves, push back and trim. Over-requirement is the #1 reason good candidates don't apply.
  • Salary transparency: recommend including a band (postings with salary get markedly more qualified applicants, and it's legally required in many regions — note this).
  • Bias check: flag anything that could screen out candidates illegally or unnecessarily (degree requirements where unneeded, citizenship, etc.).

Bonus: screening scorecard

After the JD, produce a 1–5 scorecard mapping each must-have to an interview signal, so the hiring team evaluates consistently (and defensibly).

Rules

  • Don't invent company facts — use [BRACKETS] for anything not provided.
  • This supports hiring decisions; final comp and legal compliance (e.g. pay-transparency, EEO) should be confirmed with HR/counsel for the user's jurisdiction.

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-06

  • announce the skill at startin 54 of 1637, across 21 files
  • convert legacy doc files before editingin 45 of 1637, across 7 files
  • predict questions readers might askin 42 of 1637, across 3 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test document with fresh context-less instancein 42 of 1637, across 3 files
  • ask interview questions one at a timein 42 of 1637, across 26 files
  • include exact file paths in every taskin 42 of 1637, across 15 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 1 file

Said here and by no other author read

  • produce a paste-ready job description
  • write a clear hook explaining the role
  • list concrete outcomes not vague duties
  • separate must-haves from nice-to-haves
  • strip biased or coded language
  • challenge inflated requirements

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.