Job description
Write inclusive, compelling job descriptions — role summaries, requirements, benefits, and bias-free language.From its SKILL.md
npx -y skills add inbharatai/claude-skills --skill job-descriptionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.8 KB, 321 tokens by cl100k_base, as published. Nobody here has run it
Job Description
Overview
Write inclusive, compelling job descriptions — role summaries, requirements, benefits, and bias-free language.
When to Use This Skill
Use Job Description when you need to:
- Work with job description tasks in your project or workflow
- Automate job description operations at scale
- Generate production-quality job description output quickly
Instructions
When this skill is active, Claude will:
- Understand the full context of your job description request
- Apply best practices and conventions for Business & Productivity
- Produce clean, well-structured, production-ready output
- Explain key decisions and offer alternatives where relevant
Examples
Example 1 — Basic Usage
User: Help me get started with job description.
Claude: I'll walk you through the essential steps for job description in your context...
Example 2 — Advanced Usage
User: I need a production-ready job description setup with full error handling.
Claude: Here's a complete, production-hardened job description implementation...
Guidelines
- Always validate inputs before processing
- Follow the conventions of the target platform or language
- Prefer explicit over implicit — clarity beats cleverness
- Include comments for non-obvious logic
- Suggest tests or validation steps where appropriate
Dependencies
Required: none
Platforms
Available on: claude.ai, api
Part of the claude-skills collection — 183+ skills for Claude.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most hr recruiting skills give in 321 tokens
Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07
- Quantify achievements with specific metricsin 14 of 356, across 6 files
- Keep the resume under two pagesin 14 of 356, across 6 files
- Request the full job description if not providedin 12 of 356, across 4 files
- Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
- Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
- Map candidate experience to job requirementsin 11 of 356, across 3 files
- Ask if the user wants adjustmentsin 11 of 356, across 3 files
- Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
- Request candidate background details if not providedin 10 of 356, across 2 files
- Format experience bullets as action verb plus resultin 10 of 356, across 2 files
- Ask for missing inputs before startingin 10 of 356, across 9 files
- Use exact job description terminologyin 9 of 356, across 1 file
Said here and by no other author read
- understand the full context of the request
- apply best practices for business and productivity
- produce clean, well-structured, production-ready output
- explain key decisions and offer alternatives
- validate inputs before processing
- follow the conventions of the target platform
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.