job-title-normalization
Skill9 starsChanged 5 months agoMITView on GitHub
Converts inconsistent job titles into standardized role, department, and seniority labels. Use when the user provides records with free-text titles and wants consistent role family, department, and seniority fields.
In this repository23 other files it gives its agents.
- account-prioritizationSkill
- b2b-lead-qualificationSkill
- candidate-qualificationSkill
- company-data-normalizationSkill
- company-researchSkill
- company-research-workflow-plannerSkill
- company-segmentationSkill
- competitor-researchSkill
- directory-research-plannerSkill
- duplicate-record-reviewSkill
- lead-list-analysisSkill
- lead-list-segmentationSkill
- lead-research-workflow-plannerSkill
- market-researchSkill
- outreach-brief-generatorSkill
- partner-qualificationSkill
- persona-classificationSkill
- person-researchSkill
- prospect-list-cleanupSkill
- recruiting-sourcing-plannerSkill
- research-gap-analysisSkill
- supplier-qualificationSkill
- territory-segmentationSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Do not invent seniority not implied by the title.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Job Title Normalization
Purpose
Convert inconsistent job titles into standardized role, department, and seniority labels.
When to use this skill
- Standardizing titles for segmentation or routing
- Filtering a list by seniority reliably
- Mapping titles to departments for targeting
- Cleaning multi-source contact data
When not to use this skill
- The records have no title field
- Titles are in languages you have not configured
- You need verified org-chart data
Required inputs
- Records containing job titles
Optional inputs
- A role-family taxonomy
- A seniority scale
- Department definitions
Rules
- Map to the supplied taxonomy and scale when provided.
- Preserve the original title.
- Report confidence and ambiguity.
- Do not invent seniority not implied by the title.
- Be consistent across identical titles.
Process
- Parse each title.
- Map to role family and department.
- Assign seniority.
- Record confidence and ambiguity.
- Output original and normalized values.
Output format
Return one record per title with the following fields:
- original_title
- normalized_title
- role_family
- department
- seniority
- confidence
- ambiguity_notes
Validation
- Confirm identical titles map identically.
- Confirm low-confidence rows are flagged.
- Confirm seniority is implied by the title.
Limitations
- Titles vary by company; mapping is heuristic.
- Inflated or vague titles may misstate seniority.
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
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.