agentleFS
claude-office-skillsclaude-office-skills/skills/job-description/SKILL.md

Job Description Generator

Skill433 starsChanged 10 months agoMITView on GitHub

>

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Use inclusive, bias-free language

    line 58
  2. Distinctive:

    Follow industry best practices

    line 59
  3. Distinctive:

    Use "you" instead of "the ideal candidate"

    line 116
  4. Distinctive:

    Avoid gendered language (he/she → they)

    line 117

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Generator

Generate professional, inclusive job descriptions that attract qualified candidates.

Overview

This skill helps HR professionals and hiring managers create comprehensive job postings that:

  • Clearly communicate role expectations
  • Use inclusive, bias-free language
  • Follow industry best practices
  • Attract diverse, qualified candidates

How to Use

Provide the following information:

  1. Job Title: The position name
  2. Department: Team or department
  3. Level: Entry, Mid, Senior, Lead, Director, etc.
  4. Employment Type: Full-time, Part-time, Contract
  5. Location: On-site, Remote, Hybrid
  6. Key Responsibilities: What the role will do
  7. Requirements: Must-have qualifications
  8. Nice-to-haves: Preferred qualifications
  9. Company Info: Brief about the company (optional)

Output Structure

# [Job Title]

## About [Company]
[Brief company description]

## About the Role
[2-3 sentences describing the position and its impact]

## What You'll Do
- [Responsibility 1]
- [Responsibility 2]
- [Responsibility 3]
...

## What We're Looking For

### Required
- [Requirement 1]
- [Requirement 2]
...

### Nice to Have
- [Preferred qualification 1]
- [Preferred qualification 2]
...

## What We Offer
- [Benefit 1]
- [Benefit 2]
...

## How to Apply
[Application instructions]

Best Practices

Language Guidelines

  • Use "you" instead of "the ideal candidate"
  • Avoid gendered language (he/she → they)
  • Remove unnecessary jargon
  • Be specific about requirements vs. nice-to-haves
  • Include salary range when possible (improves applications by 30%)

Red Flags to Avoid

  • "Rockstar" / "Ninja" / "Guru" → Use "Expert" or "Specialist"
  • "Fast-paced environment" → Be specific about workload
  • Excessive requirements → Limit to 5-7 must-haves
  • Vague responsibilities → Use measurable outcomes

Inclusive Language

Instead ofUse
"Young and energetic""Motivated and enthusiastic"
"Native English speaker""Fluent in English"
"Cultural fit""Values alignment"
"Digital native""Proficient with digital tools"

Examples

Example Request

Create a job description for:
- Title: Senior Frontend Developer
- Department: Engineering
- Level: Senior (5+ years)
- Type: Full-time, Remote
- Tech stack: React, TypeScript, GraphQL
- Team size: 8 engineers
- Company: B2B SaaS startup, Series B

Example Output

# Senior Frontend Developer

## About Us
We're a Series B B2B SaaS startup transforming how enterprises manage their workflows. Our engineering team of 40+ builds products used by Fortune 500 companies.

## About the Role
Join our 8-person frontend team to architect and build the next generation of our platform. You'll have significant impact on technical decisions and mentor junior developers.

## What You'll Do
- Design and implement complex UI features using React and TypeScript
- Collaborate with designers to create intuitive user experiences
- Optimize application performance and accessibility
- Contribute to our GraphQL API design
- Mentor junior developers through code reviews and pairing
- Participate in technical planning and architecture discussions

## What We're Looking For

### Required
- 5+ years of frontend development experience
- Strong proficiency in React and TypeScript
- Experience with GraphQL or similar query languages
- Track record of building accessible, performant web applications
- Excellent communication skills

### Nice to Have
- Experience with design systems
- Contributions to open source projects
- Experience at B2B SaaS companies
- Familiarity with testing frameworks (Jest, Cypress)

## What We Offer
- Competitive salary: $150,000 - $190,000
- Equity package
- Fully remote with flexible hours
- Health, dental, and vision insurance
- $2,000 annual learning budget
- Home office stipend

## How to Apply
Send your resume and a brief note about why you're interested to careers@company.com

Domain Knowledge

Job Levels (Typical)

LevelYearsScope
Entry/Junior0-2Individual tasks
Mid-level2-5Independent projects
Senior5-8Technical leadership
Staff/Lead8-12Cross-team impact
Principal/Director12+Organization-wide

Standard Benefits to Consider

  • Health insurance
  • Retirement plans (401k, pension)
  • PTO / Vacation policy
  • Remote work options
  • Professional development
  • Parental leave
  • Equipment/stipends

Limitations

  • Cannot guarantee legal compliance (have HR/legal review)
  • Salary benchmarks may not reflect local markets
  • Industry-specific requirements need domain input
  • Cannot verify company information provided

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.