Generate a clear, inclusive job description from a role title and requirements in seconds.
Produce a polished, inclusive job description that attracts diverse candidates and clearly communicates the role, responsibilities, and requirements.
When a hiring manager or recruiter needs to draft a new job description for an open role.
Analyze the following role and requirements provided by the user: $role_and_requirements
Role and requirements:
$role_and_requirementsWrite a compelling 2–3 sentence company/role introduction that conveys mission, impact, and team context without using the company name if unknown.
List 5–7 core responsibilities as concise bullet points using active verbs. Focus on outcomes and day-to-day impact, not just tasks.
Separate requirements into two groups: 'Must-Have' (3–5 non-negotiable skills or qualifications) and 'Nice-to-Have' (2–4 bonus skills). Avoid degree requirements unless strictly necessary.
Scan the full draft for exclusionary or biased language (e.g., 'rockstar', 'ninja', gendered pronouns, ageist phrases). Replace any flagged terms with neutral, inclusive alternatives.
Add a short closing section (2–3 sentences) that encourages candidates from diverse backgrounds to apply, mentions flexibility or DEI commitment if appropriate, and ends with a clear call to action.
Return the job description as structured sections in this order: Role Introduction, Responsibilities (bulleted), Requirements split into Must-Have and Nice-to-Have (bulleted), and Closing Statement. Use plain readable formatting with clear section headers. Tone should be professional yet approachable.
Copy this skill into your library to inject it into Claude, ChatGPT, and Gemini — or install your whole library as / slash commands in Claude Code and Cowork.
Get started free →Related skills
Turn account load and team capacity data into a resource plan with coverage analysis, at-risk gaps, and reallocation recommendations.
Transform raw work logs into a polished, stakeholder-ready weekly status report in minutes.
Draft a blameless postmortem from an incident timeline and impact summary, following SRE best practices.