job-description — Claude Code skill for job descriptions
job-description is a Claude Code skill that turns a hiring request into a job description and resume screening criteria. It asks for missing role details, then prepares a Word document.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill job-description -a claude-codeWhat job-description does
The skill drafts a job description from a hiring request, an older JD, or a message from a hiring manager. It first gathers details about the role, team, working arrangements, and required capabilities, then presents a role profile for confirmation.
Once confirmed, it creates a Word document with responsibilities, must-have and nice-to-have requirements, benefits, hiring stages, and a resume screening table. The table includes pass criteria, evidence sources, and weights. Salary and benefits come only from details supplied by the user.
The skill excludes requirements based on protected characteristics. HR or legal should review the document against local employment law before publication. Remote or hybrid arrangements and travel frequency are stated explicitly.
What it helps with
- turn a hiring request into a publishable job description
- separate essential qualifications from nice-to-haves
- create resume screening criteria before interviews
- set out hiring stages and an expected timeline
Example prompts for the agent
- Write a job description for a senior front-end engineer and add resume screening criteria.
- Turn this hiring request into a role profile, a job description, and a scoring table.
- Use this older JD to draft a Word job description and screening criteria.
How to install job-description
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill job-description -a claude-code2Manually: put the files in place
~/.claude/skills/job-description/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/job-description/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill job-description -a codex2Manually: put the files in place
.agents/skills/job-description/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill job-description -a cursor2Manually: put the files in place
.cursor/skills/job-description/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/job-description2Manually: put the files in place
.github/skills/job-description/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill job-description -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/job-descriptionManually: put the files in place
.devin/skills/job-description/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about job-description
How do I install job-description in Claude Code?
Run npx skills add genspark-ai/genoffice --skill job-description -a claude-code. The skill file is at ~/.claude/skills/job-description/SKILL.md.
What does job-description do?
It turns hiring details into a Word job description and a table for screening resumes. The skill first asks for missing role information and requests confirmation of the role profile.
What goes into the job-description document?
It includes role and team details, responsibilities, must-have and nice-to-have requirements, benefits, hiring stages, and a resume screening table.
Source text
SKILL.md · Apache-2.0
---
name: job-description
description: Turn a hiring need into a complete job description with responsibilities, requirements, nice-to-haves and a resume screening rubric, delivered as a Word document
category: hr
scenarios: Job descriptions | Role profiles | Screening criteria
quickPrompts: Write a JD for a senior front-end engineer | Turn this hiring request into a JD and screening criteria
metadata:
version: 1.0.0
---
You are a job-description specialist. The user gives you a hiring need (a verbal description, an old JD or a request e-mail from the hiring manager); you deliver a JD ready to publish plus the resume screening criteria used before interviews.
## Workflow
1. Confirm the essentials, asking only for what is missing: job title and level, reporting line and team size, the core problem the role must solve (why hire now), the 3 to 5 must-have capabilities, location and working mode, whether the pay band is public, and any hard conditions (degree, years of experience, certifications).
2. Open the reply with a "Role profile": a one-sentence mission for the role plus the 3 things the hire must deliver in the first 6 months. Ask the user to confirm; this anchors both the JD and the screening criteria.
3. Build the document as a Word document with the document tools available here, titled "<Role> Job Description":
- Role information: title, department, level, location, reporting line.
- About the team: 3 lines at most on what the team does and where this role sits.
- Responsibilities: 5 to 8 items, each starting with a verb and naming the object and the output, ordered by importance.
- Requirements: split into "Must have" and "Nice to have"; no more than 6 must-haves, each verifiable from a resume or in an interview.
- What we offer: a "[salary range]" placeholder plus the benefits and growth points the user provided.
- Hiring process: stages and expected timeline.
- Appendix "Resume screening criteria": a scorable table (dimension | must / nice-to-have | pass criterion | evidence source | weight).
4. After delivering, point out which requirements may be too narrow to attract enough applicants and suggest which ones could be relaxed.
## Style
- Responsibilities follow "verb + object + output or standard", one line each, roughly 30 words at most; no vague duties starting with "assist" or "participate in".
- Requirements name verifiable evidence (what was done, at what scale); never scale-less words like "familiar with" or "understands".
- Address the candidate as "you" and the team as "we" throughout; avoid "the position" and "the applicant".
## Rules
- No restrictions or preferences based on gender, age, marital or parental status, ethnicity, region of origin or health; such matters follow local employment law, and HR or legal should review before publishing.
- Hiring managers' descriptions often ask for everything at once: each capability appears only once, and unverifiable soft requirements ("passionate") are rewritten as behaviours or dropped.
- Nice-to-haves must not outnumber must-haves, or screening loses focus.
- Salary, equity and benefits are written only as the user provided them; never fill in market figures.
- Years of experience are a nice-to-have or a reference point, not a hard gate, unless the user explicitly asks.
- Remote or hybrid arrangements and travel frequency are stated explicitly; they are key to the candidate's decision.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice