job-description-writer
Skill22 starsChanged 3 months agoMITView on GitHub
Writes inclusive, accurate, and compelling job descriptions with a clear role summary, outcome-oriented responsibilities, must-have vs. nice-to-have requirements, impact framing, and compensation/logistics. Use this skill when the user asks to "write a job description", "create a job posting", "draft a JD", "post a role", "rewrite this job ad to be more inclusive", "turn this requirements list into a posting", or needs help defining responsibilities, qualifications, leveling, or salary ranges for a hire.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- osamabinjannat/remote-hiring-skillstheir own version, first seen Oct 25, 2026
- JayRHa/agent-skillsword for word, first seen Oct 15, 2026
- edu6565/claude-skillstheir own version, first seen Oct 11, 2026
- SkillMedev/people-ops-recruitingtheir own version, first seen Oct 5, 2026
- poorvith-mp/skills-businesstheir own version, first seen Aug 19, 2026
- Uhudsavasindankacanokcu2/recruiting-skills-for-claudetheir own version, first seen Jun 18, 2026
Other versions7 projects use a version of this.
Word for word · 2
- JayRHa/agent-skills★ 12100% same
- JayRHa/AgentSkills★ 12100% same
Edited · 0
None found.
Wrote their own version · 5
- Uhudsavasindankacanokcu2/recruiting-skills-for-claude★ 3same name
- osamabinjannat/remote-hiring-skills★ 1same name
- poorvith-mp/skills-business★ 1same name
- edu6565/claude-skills★ 0same name
- SkillMedev/people-ops-recruiting★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository194 other files it gives its agents.
- 0-templateSkill
- ab-test-analyzerSkill
- academy-guideSkill
- add-to-my-skillsSkill
- adr-authorSkill
- ai-tools-setupSkill
- algorithmic-artSkill
- api-and-interface-designSkill
- api-designerSkill
- api-docs-writerSkill
- apple-store-submitSkill
- aws-cost-optimizerSkill
- bash-script-hardeningSkill
- blog-post-writerSkill
- book-summarizerSkill
- branch-cleanupSkill
- brand-copy-landingSkill
- brand-copySkill
- brand-designSkill
- brand-guidelinesSkill
- browser-testing-with-devtoolsSkill
- canvas-designSkill
- changelog-generatorSkill
- changelog-keeperSkill
- chart-chooserSkill
- ci-cd-and-automationSkill
- ci-fix-loopSkill
- claude-apiSkill
- cloudflare-block-countriesSkill
- coderabbitloopSkill
- code-review-and-qualitySkill
- code-reviewerSkill
- code-simplificationSkill
- codexloopSkill
- comms-notionSkill
- comms-slackSkill
- comms-whatsappSkill
- competitive-analysisSkill
- concept-explainerSkill
- constraint-driven-developmentSkill
- context-engineeringSkill
- context-repoSkill
- cover-letter-writerSkill
- crash-courseSkill
- cron-schedulerSkill
- data-digestSkill
- data-pipeline-architectSkill
- debug-detectiveSkill
- debugging-and-error-recoverySkill
- decision-matrixSkill
- dependabot-triageSkill
- dependency-upgraderSkill
- deprecation-and-migrationSkill
- dev-instantdbSkill
- discernment-nudgeSkill
- doc-coauthoringSkill
- dockerfile-proSkill
- docs-index-keeperSkill
- documentation-and-adrsSkill
- docxSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Always optimize for: clarity, inclusivity, accuracy, and measurable impact.
- Very specific: line 20
Define outcomes first, then responsibilities: Before listing duties, write what success looks like at 30/90/365 days.
- Distinctive: line 22
Split requirements into Must-have vs. Nice-to-have: Keep must-haves to 4-7 genuinely non-negotiable items.
- Very specific: line 26
Scrub for bias and accessibility: Run scripts/jd_lint.py to flag biased/coded terms, gendered language, jargon, requirement inflation, and …
- Distinctive: line 59
Avoid the trap of "years of experience" as the primary gate.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Job Description Writer
Overview
Keywords: job description, JD, job posting, job ad, role, hiring, recruiting, responsibilities, requirements, qualifications, inclusive hiring, salary range, level, seniority, EEO, talent acquisition.
This skill produces job descriptions that attract qualified, diverse candidates and accurately represent the role. A strong JD does three jobs at once: it markets the role and company, it filters for fit (without over-filtering), and it sets expectations for the first year. The most common failure modes are inflated requirement lists that deter qualified candidates (especially underrepresented groups), vague responsibilities that describe activity instead of outcomes, and biased or coded language.
Always optimize for: clarity, inclusivity, accuracy, and measurable impact.
Workflow
- Gather inputs. Collect the essentials before writing. If the user hasn't provided them, ask concise clarifying questions (batch them). Minimum needed: job title, level/seniority, team & reporting line, top 3-5 outcomes the hire owns, location/remote policy, employment type, and any compensation data. See
references/intake-questions.mdfor the full checklist. - Define outcomes first, then responsibilities. Before listing duties, write what success looks like at 30/90/365 days. Convert each outcome into 5-8 responsibility bullets phrased as ownership ("Own X", "Drive Y", "Ship Z") rather than activity ("Responsible for attending meetings").
- Split requirements into Must-have vs. Nice-to-have. Keep must-haves to 4-7 genuinely non-negotiable items. Everything aspirational goes under nice-to-have. Strip proxy requirements (degree, exact years) unless legally or functionally essential. See
references/inclusive-language.mdfor substitutions. - Add impact + level context. State why the role exists, who it affects, and how performance is measured. Calibrate scope language to the level (see the leveling table below).
- Scrub for bias and accessibility. Run
scripts/jd_lint.pyto flag biased/coded terms, gendered language, jargon, requirement inflation, and missing sections. Apply fixes. - Add logistics, comp, and EEO statement. Include salary range (transparency is legally required in many jurisdictions and improves applies), benefits highlights, application process, and an equal-opportunity statement.
- Assemble using the template. Fill
templates/job-description-template.md. Keep total length to roughly 400-700 words for the body; longer postings reduce completion rates.
Structure of a Great JD
| Section | Purpose | Keep it |
| Title | Searchable, standard, level-clear | "Senior Backend Engineer" not "Backend Ninja" |
| Hook (2-3 sentences) | Why the role + company matter | Specific, no buzzword soup |
| About the team | Context and mission | 2-4 sentences |
| What you'll do | Outcome-based responsibilities | 5-8 bullets, verb-led |
| What you'll bring | Must-have requirements | 4-7 bullets, no inflation |
| Nice to have | Aspirational extras | Optional, clearly labeled |
| Impact / success | How impact is measured | 30/90/365 or KPIs |
| Compensation & benefits | Range + highlights | Be transparent |
| Logistics | Location, type, process | Clear next steps |
| EEO statement | Inclusion commitment | Required |
Leveling / Scope Calibration
Match the language to the level so candidates self-select accurately.
| Level | Scope verb | Typical responsibility framing | Typical experience signal |
| Junior / IC1 | Contributes to | "Complete well-scoped tasks with guidance" | 0-2 yrs equivalent |
| Mid / IC2-3 | Owns | "Own features end-to-end; unblock yourself" | 2-5 yrs equivalent |
| Senior / IC4 | Drives | "Drive projects across the team; mentor others" | 5+ yrs equivalent |
| Staff / IC5+ | Leads / influences | "Set technical direction; influence org strategy" | Deep domain mastery |
| Manager | Builds & develops | "Hire, grow, and lead a team; own delivery & growth" | Prior leadership |
Avoid the trap of "years of experience" as the primary gate. Prefer demonstrated capability statements.
Worked Example
See examples/jd-example.md for a raw input (messy requirements dump) transformed into a finished, inclusive job description, including before/after of biased lines.
Best Practices
- Outcomes over activities. "Reduce checkout latency by owning the payments service" beats "Work on backend systems."
- Cap the must-have list. Research shows candidates (women especially) often don't apply unless they meet ~100% of listed requirements. Shorter lists widen the pool.
- Use "you" and active voice. It reads as an invitation, not a spec sheet.
- Show the salary range. Transparency increases qualified applies and is legally mandated in many places.
- Name concrete tech/tools but mark transferable skills as acceptable ("or similar").
- Lead with mission and team so candidates understand the "why."
- One title, standard naming so the role is searchable on job boards.
- Run the linter (
scripts/jd_lint.py) before finalizing; treat it as a checklist, not gospel.
Common Pitfalls
- Requirement inflation: listing "nice-to-haves" as "must-haves" (e.g., 5 frameworks, a degree, and 10 years for a mid role). Move them or cut them.
- Coded/gendered language: "rockstar," "ninja," "aggressive," "dominant," "he/his," "young and energetic." Replace per
references/inclusive-language.md. - Wall-of-text responsibilities describing process instead of impact.
- Missing comp or EEO sections — both hurt apply rates and can create legal exposure.
- Generic hooks ("We are a fast-paced, dynamic team...") that say nothing. Be specific about the product, the team, and the problem.
- Mismatched level signals: senior pay with junior scope, or vice versa, causes drop-off and bad hires.
- Accessibility-blocking phrasing: "must be able to lift 50 lbs" or "valid driver's license" when not essential to the job can exclude qualified candidates and raise ADA concerns — only include genuine bona fide requirements.
Files
references/intake-questions.md— questions to ask before writing.references/inclusive-language.md— biased→inclusive substitution tables and rules.scripts/jd_lint.py— stdlib-only linter that flags issues in a draft JD.templates/job-description-template.md— fill-in template.examples/jd-example.md— full before/after worked example.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

