Individual skill

job-description-writer

Draft an inclusive, role-relevant, level-calibrated job posting from a hiring manager's role brief. Use when an employer is writing or revising a job description, JD, or job posting - you have a role brief, leveling rubric, or comp band and need outcome-based requirements, plain compensation/logistics, and inclusive tone. Do NOT use when tailoring a candidate's resume or cover letter to a posting - use job-application instead.

skills/job-description-writer/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Job Description Writer

Turn an employer's role brief into a posting a strong candidate reads to the end and a fair process can be built on. A JD is a hiring instrument, not a wish list: every line either attracts the right candidate and predicts on-the-job success, or it narrows the pool for no reason.

## Workflow

1. Confirm the role brief and level. Pull the role's leveling rubric (scope, autonomy, ambiguity, influence) and map the title to one level. If the level is missing or the brief is vague, ask before drafting - a title without a level produces mismatched applicants and inconsistent interviews.
2. Write 4-6 outcome statements, not task lists. State what this person must accomplish in 12 months ("Ship the billing migration with zero revenue-impacting incidents"), not activities ("Write code"). Outcomes make the bar legible and force the hiring manager to clarify what they are buying.
3. Separate must-haves from bonus. Cap must-haves at 5-7 and include only what is genuinely needed on day one. Move everything else to "bonus." Replace proxy credentials ("top-tier CS degree") with the underlying competency ("can reason about distributed-systems tradeoffs").
4. State experience as a signal, not a gate. Frame years of experience as a soft signal, never a hard requirement. Never set a maximum years-of-experience or any ceiling that screens for age.
5. State compensation and logistics plainly. Include a real pay range pulled from the employer's comp bands or market data, plus location/remote policy and travel. A posted range whose top is more than roughly 50% above its bottom reads as evasive and depresses applications; if the honest band is that wide, the role is probably spanning two levels - split it or narrow it. Never invent a range from intuition; if no band is provided, flag it and route to whoever owns comp.
6. Set human, inclusive tone. Use plain second-person language. Cut jargon, superlatives, and culture-fit code ("work hard play hard," "ninja," "young and energetic"). State concrete inclusion and accommodation commitments. Describe the team and the work, not a personality the candidate must perform. Keep the whole posting in the 300-700 word range - long enough to be concrete, short enough that candidates read to the compensation line.
7. Hand off for ownership. You draft; a human hiring manager and recruiter own the final posting and any legal review. Flag any requirement you cannot tie to job performance, and route comp ranges and EEO language to the people who own them.

## Deliverable