Free skill · October 2, 2026

Candidate Record Version Match

Keep candidate resume versions and identifiers separate before interview evidence is reused.

Keep candidate resume versions and identifiers separate before interview evidence is reused. The download provides a specific review process. It does not make decisions or act in an account.

Download the free skill

One complete Markdown file. No subscription, checkout or fabricated setup files.

Download SKILL.md

What to provide

Approved candidate IDs, resume versions, receipt times, interview references and retention policy.

How it works

  1. Match by verified candidate ID. Similar names are insufficient.
  2. List every document version and its source timestamp. Do not overwrite older evidence silently.
  3. Flag an interview note citing a superseded or unidentified resume; ask which version the interviewer used.
  4. Return a version crosswalk and unresolved identity gaps. Do not rank, reject, merge ATS records or contact applicants.

The output

candidate ID | document version | received | interview reference | mismatch | reviewer question

Worked fictional example

Two fictional Alex records have different candidate IDs. Do not merge. Note N1 quotes resume v1 while current v2 differs; preserve both and flag the version gap.

Checks and limits

Preserve source versions and original values. Unknowns stay unknown. Use a qualified reviewer for regulated, legal or hiring decisions. No send, share, account change, schedule, ledger update or payment is authorized. No live account test is claimed.

More recruiters workflows · How-to guides

Method: reviewed source. Demand lead: GSC ai agent application screening1,hiringpipeline1. These are site-query cluster impressions and method evidence, not exact new-topic monthly search volume or a traffic promise. Checked October 2, 2026.