resume-template-semantic-mapping

Map candidate resume content models into verified resume template semantic slot manifests.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/rickvang/Persona-Library --skill resume-template-semantic-mapping-rickvang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resume-template-semantic-mapping
Source: https://github.com/rickvang/Persona-Library/tree/main/.agents/skills/resume-template-semantic-mapping
Command: npx skills add https://github.com/rickvang/Persona-Library --skill resume-template-semantic-mapping-rickvang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rendering a candidate's normalized resume content through a reusable resume Template often loses material content, flattens employer/client structure, or invents unsupported claims. This Skill maps a private Resume Content Model into a verified Template's semantic slot manifest while preserving evidence traceability, chronology, and candidate-specific structure. ## Core Features & Use Cases - Semantic slot mapping: Match each content node to a legitimate Template slot by documented purpose, classifying every material source as mapped, omitted_with_reason, blocked, unmapped, or not_applicable. - Structural and evidence fidelity: Preserve employer-of-record versus client hierarchy, separate employment periods, dates, metrics, and an active Candidate Baseline Resume's protected career spine. - Layered validation and loss visibility: Run candidate/model conformance, Template slot conformance, evidence integrity, and isolation checks, surfacing Template mismatches instead of silently dropping content. - Use Case: When switching a candidate's approved resume content to a materially different layout from the template-library, produce a mapping table showing exactly where each achievement, role, and certification landed and why anything was omitted. ## Quick Start Map my current Resume Content Model into the verified resume Template's slot manifest and show me the material mapping table with any unmapped or blocked content.

Frequently Asked Questions about resume-template-semantic-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map resume content into a new resume template without losing information?▼

Map each content node to a template slot by semantic purpose rather than available space, then classify every material source as mapped, omitted_with_reason, blocked, unmapped, or not_applicable. This makes semantic loss visible before composition instead of silently dropping content.

What is a resume template slot manifest?▼

A slot manifest (slot-map.json) is a machine-readable file shipped with a verified resume Template that declares each semantic slot's documented purpose and the Resume Content Model version it targets. Mapping matches candidate content nodes to these slots by meaning.

Can this handle candidates with multiple employment periods at one employer?▼

Yes. The mapping preserves employer-of-record distinct from clients and keeps separate employment periods separate when evidence or standing decisions require it. Merging repeated periods for visual convenience is explicitly flagged as a failure pattern.

Does a successful template mapping mean the resume is ATS-compatible?▼

No. Semantic mapping success is not reported as ATS, accessibility, visual, parser, or export success unless those checks were separately run on the actual output. Downstream validation results and what was not checked are recorded explicitly.

When should resume template semantic mapping not be used?▼

Do not use it to discover candidate evidence, decide whether a claim is true, design a new Template from scratch, create candidate facts, or replace ATS, document, and accessibility review. It is a bounded transformation aid, not an evidence or design tool.