Inputs
Provide these when prompted. The skill asks for anything missing before it runs.
Required
- Records containing job titles
Optional
- A role-family taxonomy
- A seniority scale
- Department definitions
Agent Skill
Job Title Normalization
Convert inconsistent job titles into standardized role, department, and seniority labels.
Version 1.0 Updated June 2026 SKILL.md MIT 6 min read
Overview
What this skill does
Free-text job titles are wildly inconsistent — "VP, Eng", "Head of Engineering", "Engineering Leader" — which breaks segmentation, routing, and seniority filtering.
This skill maps each title to a standardized role family, department, and seniority, with a confidence level and ambiguity notes so edge cases are visible rather than silently miscategorized.
When to use it
Best used for
- Standardizing titles for segmentation or routing
- Filtering a list by seniority reliably
- Mapping titles to departments for targeting
- Cleaning multi-source contact data
Know the limits
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
Outputs
One record per title with a consistent, inspectable schema.
original_titleThe input title, preserved.
normalized_titleA standardized title string.
role_familye.g. Engineering, Sales, Marketing.
departmentThe mapped department.
senioritye.g. IC, Manager, Director, VP, C-level.
confidenceMapping confidence.
ambiguity_notesWhy a title was hard to classify.
Example
Example
A messy title mapped.
Input
title: VP, Eng & PlatformOutput
original_title: VP, Eng & Platform
normalized_title: VP of Engineering
role_family: Engineering
department: Engineering
seniority: VP
confidence: high
ambiguity_notes: Covers platform scope; mapped to EngineeringThe compressed title becomes filterable role/department/seniority fields, with the multi-scope note preserved for anyone reviewing edge cases.
Setup
How to use the skill
General steps first, then notes for specific clients where verified.
- 1Download the file using the button below, or copy the Markdown.
- 2Place it in a directory named after the skill (e.g. skill-name/).
- 3Make sure the filename stays exactly SKILL.md.
- 4Add any references or assets included with the package.
- 5Load the skill into a compatible agent and provide the required inputs.
Claude Code
- 1Create a folder for the skill and save SKILL.md inside it.
- 2Place the folder where your project's skills are discovered.
- 3Reference the skill when you want it applied to your data.
Other compatible clients
- 1Confirm the client supports the open Agent Skills format.
- 2Load the SKILL.md file as instructed by that client.
- 3If skills are not auto-loaded, paste the Markdown as instructions.
Source
Full SKILL.md source
Read the rendered skill or copy the complete Markdown. The download is generated from this exact source.
Version 1.0 SKILL.md ~2 KB MIT
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.
Before you rely on it
Safety and limitations
- Titles vary by company; mapping is heuristic.
- Inflated or vague titles may misstate seniority.
- Review the output before acting on it.
- Do not upload confidential datasets to an external model without authorization.
- Outputs depend on the model and the source data and are not guaranteed to be accurate.
History
Changelog
- v1.0June 2026
- Initial release.
Questions
Agent Skill FAQ
How does it handle vague or made-up titles?
It maps to the closest standard role, department, and seniority it can evidence, and flags low-confidence or ambiguous titles (for example "Ninja" or "Guru") rather than forcing a label.
Can I supply my own role taxonomy?
Yes. Provide a role-family list and seniority scale and the skill maps titles to your standard.
Do I need ProfileSpider to use this skill?
No. The skill works on any compatible data. ProfileSpider is one convenient way to produce that structured input.
Does running this skill send data to ProfileSpider?
No. Downloading or copying the file does not send any data to ProfileSpider. What happens afterward depends on the AI service you load it into.
Are Agent Skills the same as prompts?
No. A skill is a structured, reusable package — task, inputs, rules, process, and output format — so the workflow runs consistently and can be shared, versioned, and edited.