Job description analyzer
Parses a raw job description into a structured TargetProfile — role, seniority, must-have vs nice-to-have requirements, hard/soft skills, responsibilities, ATS keywords, and a truthful crossover (their-term ↔ your-term) map. Distilled from "Resumes For Dummies" (AI-era ed.). Built for automated pipelines (e.g. JobHunter) as the shared front-end that feeds both resume tailoring and scoring. Use this skill when: - Turning a job posting into structured requirements before tailoring a resume - Separating must-have from nice-to-have qualifications - Splitting hard skills (tools/certs) from soft skills - Extracting ATS keywords to mirror truthfully - Inferring a role's target seniority and focus - Building a crossover map between a JD's wording and a candidate's vocabulary - Providing a TargetProfile to resume-content-writer or resume-fit-scorerFrom its SKILL.md
npx -y skills add ebarti/skills --skill job-description-analyzerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.7 KB, 416 tokens by cl100k_base, as published. Nobody here has run it
job-description-analyzer
Converts a messy job posting into one clean, machine-usable TargetProfile: what's required vs preferred, the hard and soft skills, the responsibilities, the exact ATS keywords to mirror, the inferred seniority/focus, and a truthful crossover map. This is the shared source of truth so tailoring and scoring agree on the target. Built from "Resumes For Dummies" (AI-era ed.), chapters 1, 3, 5, 6.
Role in the JobHunter pipeline
[job-description-analyzer] → resume-content-writer → resume-fit-scorer
TargetProfile ───────────────┴───────────────────────┘
(one source of truth feeds both tailoring and scoring)
See workflows/analyze-job-description.md for the full I/O contract and the TargetProfile schema.
Quick Start
- Read
guidelines.md— it routes from your task/symptom to the right files. - For an end-to-end analysis, follow
workflows/analyze-job-description.md. - Load only the reference files the guidelines point to.
- Emit a
TargetProfile(or the caller'soutput_schema); keep crossover mappings truthful.
Contents
References
| Category | Files | Purpose |
|---|---|---|
references/requirement-extraction/ | knowledge, rules, examples | JD anatomy; must vs nice; hard vs soft skills; seniority inference |
references/keywords-and-crossover/ | knowledge, rules, examples | ATS keywords; crossover mapping; over-cloning risk |
Workflows
| Task | Workflow |
|---|---|
| Analyze a JD into a structured TargetProfile | workflows/analyze-job-description.md |
Guidelines
See guidelines.md for task/symptom-based file selection, a decision tree, the full file index, and common combinations.
What ships with it: 8 files
38.2 KB alongside SKILL.md
references/
workflows/
- guidelines.md4.3 KB
Gives 0 of the 12 instructions most hr recruiting skills give in 416 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
- Read the guidelines file
- Follow the end-to-end analysis workflow
- Load only reference files the guidelines point to
- Emit a TargetProfile or the caller output schema
- Keep crossover mappings truthful
- Split hard skills from soft skills
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.