agentleFS
nisarthnisarth/claude-skills-store/skills/human-resources/job-description/SKILL.md

job-description

Skill1 starsChanged 7 months agoMITView on GitHub

Write job descriptions with role summary, responsibilities, requirements, benefits, and inclusive language. Trigger with "write a JD for", "job description for", "job posting for", or when creating or revising a role listing for any position.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 16 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 16

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write clear, compelling, and inclusive job descriptions covering role summary, key responsibilities, required and preferred qualifications, …

    line 30
  2. Distinctive:

    Start each with an action verb

    line 68
  3. Distinctive:

    Avoid coded language: "rockstar", "ninja", "crushing it", "fast-paced" (signals bro culture)

    line 103
  4. Distinctive:

    Remove age-coded terms: "digital native", "young and energetic"

    line 104
  5. Distinctive:

    Check requirement inflation: does this role really need 10 years of experience?

    line 105
  6. Distinctive:

    Use "you" language to make the reader feel addressed personally

    line 106
  7. Distinctive:

    Use standard job titles that candidates actually search for

    line 111
  8. Distinctive:

    Keep the posting under 700 words (longer postings get fewer applications)

    line 113
  9. Distinctive:

    Use bullet points, not paragraphs, for scanability

    line 115
  10. Distinctive:

    Use standard job titles. "Growth Hacker" gets fewer applicants than "Growth Marketing Manager" because candidates do not search for …

    line 183
  11. Distinctive:

    Keep required qualifications to 5-7 items maximum.

    line 184
  12. Distinctive:

    Use experience ranges ("3-5 years") rather than minimums ("5+ years").

    line 185
  13. Distinctive:

    Do not require a degree unless legally necessary for the role.

    line 186
  14. Distinctive:

    Avoid superlatives and absolutes: "must be the best", "world-class only".

    line 189
  15. Distinctive:

    Test the JD against a readability score.

    line 190
  16. Distinctive:

    Update job descriptions at least annually, even for existing roles.

    line 191

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Job Description Writer

Write clear, compelling, and inclusive job descriptions covering role summary, key responsibilities, required and preferred qualifications, compensation, benefits, and company information.

Workflow

Step 1: Gather Role Information

Collect the following (ask if not provided):

Required:

  • Job title (use standard industry titles, not creative alternatives)
  • Department and team
  • Reporting structure (who does this role report to)
  • Level and seniority

Role definition:

  • Primary purpose of the role (1-2 sentences)
  • Top 5-8 responsibilities (what will they spend their time doing)
  • Key outcomes (what does success look like in 6-12 months)
  • Team size and dynamics
  • Required qualifications (hard requirements, not wishlists)
  • Preferred qualifications (nice-to-haves, not disguised requirements)

Logistics:

  • Location (on-site, hybrid, remote, specific office)
  • Employment type (full-time, part-time, contract)
  • Travel requirements
  • Salary range (include if required by jurisdiction or company policy)

Step 2: Write the Job Description

Structure the JD with these sections:

  1. Role Summary (3-4 sentences):
    • What the role does and why it matters
    • Key impact areas
    • What makes this opportunity compelling
  2. What You'll Do (5-8 bullets):
    • Start each with an action verb
    • Be specific about scope and ownership
    • Order by importance/time allocation
    • Include cross-functional collaboration points
  3. What We're Looking For (required qualifications):
    • Years of experience (use ranges, not minimums)
    • Technical skills and domain knowledge
    • Education (only if genuinely required)
    • Certifications (only if legally required)
  4. Nice to Have (preferred qualifications):
    • Additional skills that differentiate candidates
    • Industry experience
    • Tools and technologies
  5. What We Offer (compensation and benefits):
    • Salary range (if disclosable)
    • Equity or bonus structure
    • Key benefits highlights
    • Growth and development opportunities
  6. About [Company] (2-3 sentences):
    • Mission and what the company does
    • Team culture and values
    • Stage, size, and traction
  7. Equal Opportunity Statement

Step 3: Apply Inclusive Language

Review and revise for inclusivity:

  • Replace gendered language: "he/she" to "they", "manpower" to "workforce"
  • Reduce unnecessary requirements: degrees when experience suffices, exact years when ranges work
  • Avoid coded language: "rockstar", "ninja", "crushing it", "fast-paced" (signals bro culture)
  • Remove age-coded terms: "digital native", "young and energetic"
  • Check requirement inflation: does this role really need 10 years of experience?
  • Use "you" language to make the reader feel addressed personally
  • Limit required qualifications to genuine must-haves (research shows women apply when meeting 100% of requirements; men apply at 60%)

Step 4: Optimize for Discoverability

  • Use standard job titles that candidates actually search for
  • Include relevant keywords naturally
  • Keep the posting under 700 words (longer postings get fewer applications)
  • Front-load the most compelling information
  • Use bullet points, not paragraphs, for scanability

Output Format

## [Job Title]

**Department**: [Department] | **Location**: [Location] | **Type**: [Full-time/Part-time/Contract]
**Reports to**: [Manager Title]

### About the Role

[3-4 sentence summary of what this role does, why it matters, and what
makes it an exciting opportunity]

### What You'll Do

- [Responsibility 1 — action verb, specific scope]
- [Responsibility 2 — action verb, specific scope]
- [Responsibility 3 — action verb, specific scope]
- [Responsibility 4 — action verb, specific scope]
- [Responsibility 5 — action verb, specific scope]

### What We're Looking For

- [X-Y years of experience in relevant area]
- [Technical skill or domain knowledge]
- [Communication or collaboration requirement]
- [Additional hard requirement]

### Nice to Have

- [Preferred skill 1]
- [Preferred skill 2]
- [Preferred skill 3]

### What We Offer

- [Salary range, if applicable]
- [Key benefit 1]
- [Key benefit 2]
- [Key benefit 3]
- [Growth opportunity]

### About [Company]

[2-3 sentences about company mission, culture, and what makes it
a great place to work]

---

*[Company] is an equal opportunity employer. We celebrate diversity and
are committed to creating an inclusive environment for all employees.*

Examples

User: "Write a job description for a Senior Backend Engineer." Action: Generate full JD with backend-specific responsibilities (API design, system architecture, mentoring), technical requirements (languages, frameworks, distributed systems), and growth narrative.

User: "JD for a Customer Success Manager, remote, $80-100K." Action: Generate JD emphasizing relationship management, account health, and expansion metrics. Include remote work details and salary range.

User: "Review this JD for inclusive language." Action: Audit the existing JD for gendered terms, coded language, inflated requirements, and exclusionary patterns. Provide specific rewrites.

Best Practices

  • Use standard job titles. "Growth Hacker" gets fewer applicants than "Growth Marketing Manager" because candidates do not search for creative titles.
  • Keep required qualifications to 5-7 items maximum. Every additional requirement reduces the applicant pool.
  • Use experience ranges ("3-5 years") rather than minimums ("5+ years"). Ranges signal that you value different backgrounds.
  • Do not require a degree unless legally necessary for the role. Many excellent candidates are self-taught or have non-traditional backgrounds.
  • State the salary range. Postings with salary ranges get 30% more applications and reduce time-to-fill. Where legally required, omitting it creates compliance risk.
  • Front-load the "What You'll Do" section with the most interesting and impactful work. The first two bullets determine whether candidates keep reading.
  • Avoid superlatives and absolutes: "must be the best", "world-class only". These discourage qualified candidates who do not self-select as elite.
  • Test the JD against a readability score. Aim for 8th-grade reading level. Complex language discourages ESL candidates.
  • Update job descriptions at least annually, even for existing roles. Role scope evolves faster than documentation.
  • Include "how to apply" instructions if the application process is not obvious.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.