agentleFS
Sign inStart free
ebartiebarti/skills/job-description-analyzer/SKILL.md

job-description-analyzer

Skill1 starsChanged 6 months agoMITView on GitHub

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.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read guidelines.md — it routes from your task/symptom to the right files.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read guidelines.md — it routes from your task/symptom to the right files.
  2. For an end-to-end analysis, follow workflows/analyze-job-description.md.
  3. Load only the reference files the guidelines point to.
  4. Emit a TargetProfile (or the caller's output_schema); keep crossover mappings truthful.

Contents

References

CategoryFilesPurpose
references/requirement-extraction/knowledge, rules, examplesJD anatomy; must vs nice; hard vs soft skills; seniority inference
references/keywords-and-crossover/knowledge, rules, examplesATS keywords; crossover mapping; over-cloning risk

Workflows

TaskWorkflow
Analyze a JD into a structured TargetProfileworkflows/analyze-job-description.md

Guidelines

See guidelines.md for task/symptom-based file selection, a decision tree, the full file index, and common combinations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free