← ClaudeAtlas

job-descriptionlisted

Write professional job descriptions for both technical and non-technical positions. Uses competency-based framework for technical roles (identifying 4-6 core competencies with proficiency levels) and outcome-based framework for non-technical roles (action + object + purpose). Checks inclusive language, flags requirements inflation (>8 requirements), and invokes compliance-check validation before final output. Auto-detects conversation language for Italian/English output. Integrates with **~~knowledge base** for existing JD templates. Use when the user says 'write a job description', 'create a JD', 'job posting for', 'descrizione del lavoro', 'annuncio di lavoro', 'scrivi annuncio', or mentions creating a position listing.
MrBogomips/claude-code · ★ 0 · AI & Automation · score 72
Install: claude install-skill MrBogomips/claude-code
# Job Description — Professional JD Generator ## 1. Overview This skill writes professional job descriptions for technical and non-technical positions. It applies two distinct frameworks depending on role type: - **Competency-based framework** (technical roles) — identifies 4-6 core competencies with proficiency levels (foundational, intermediate, advanced, expert) and behavioral indicators - **Outcome-based framework** (non-technical roles) — frames responsibilities as action + object + purpose with measurable success metrics The skill auto-detects language from the conversation and produces output in the detected language. Supported languages: English (`en`) and Italian (`it`). When language is ambiguous, the skill asks the user to choose. **Output file:** `{role}-job-description.md` **Connector support:** Skills degrade gracefully without connectors. See `CONNECTORS.md` for the full registry. - If **~~knowledge base** is connected: search for existing JD templates, corporate career page guidelines, and brand voice standards - If no connector is available: ask the user for company context, templates, and brand guidelines manually --- ## 2. Pipeline ### Step 1 — Role Analysis Gather the essential role parameters through conversation: 1. **Role type**: technical, non-technical, or hybrid 2. **Job title**: proposed title (validate for gender neutrality) 3. **Department / team**: organizational placement 4. **Location**: on-site, hybrid, remote (specify geographic c